Assalamualaikum everyone... (",)
Today is 29/08/2007 and this is break week...
I am preparing my words to interview Puan Badariah on 4/09/2007 (Tuesday)..
All the question have been prepared by me, myra and zura just before the break begin. But i think it still need to be modify a little bit...
I can't wait for the interview because we need Puan Badariah requirement, and c2d's team are really enthusiastic in creating this portal.
Have a nice holiday to all but still dont forget to visit our blog.
n u r u l ~~ A man is as old as he feels himself to be.
Wednesday, August 29, 2007
(",) Hye hye hye
Assalamualaikum and hye everyone (",)
For 23/08/2007 class, we learnt Chapter 5 which is about :
* Design Evaluation and Valid Action
* Characteristics of Good Design
* Technique for Improving Design
Puan Badariah also showed us the example of good SRS that have done by our foreigner student Adib and Nazamin. Puan Badariah told us to see them for an advice or tips to come out with good SRS.
That's all for today class...
Stay tune for more updated post from my teammate (",)
n u r u l ~~ Danger and delight grow on one stalk.
For 23/08/2007 class, we learnt Chapter 5 which is about :
* Design Evaluation and Valid Action
* Characteristics of Good Design
* Technique for Improving Design
Puan Badariah also showed us the example of good SRS that have done by our foreigner student Adib and Nazamin. Puan Badariah told us to see them for an advice or tips to come out with good SRS.
That's all for today class...
Stay tune for more updated post from my teammate (",)
n u r u l ~~ Danger and delight grow on one stalk.
(",) Exercise Week
Assalamualaikum and hello everyone... (",)
For the class on 16/08/2007, Puan Badariah remind us about dressing and she gave us 'black and white' Dress Code for student. Puan Badariah promised to us that she want to give us the Dress Code with color printed later on.
Puan Badariah gave us exercise about Use-Case Diagram. We've done it together gather in the class. There is two questions and we did the first question which is about Jenny Legal Investigator Services. Puan Badariah remind us to use VERB only when it comes to Use-Case Diagram.
At the end of the class, Puan Badariah want us to find any book about statechart and she want us to do the second question of the exercise.
p/s : sorry for this late post , because there is a problem during sending this.
Stay tune right here...
n u r u l ~~ A full cup must be carried steadily.
For the class on 16/08/2007, Puan Badariah remind us about dressing and she gave us 'black and white' Dress Code for student. Puan Badariah promised to us that she want to give us the Dress Code with color printed later on.
Puan Badariah gave us exercise about Use-Case Diagram. We've done it together gather in the class. There is two questions and we did the first question which is about Jenny Legal Investigator Services. Puan Badariah remind us to use VERB only when it comes to Use-Case Diagram.
At the end of the class, Puan Badariah want us to find any book about statechart and she want us to do the second question of the exercise.
p/s : sorry for this late post , because there is a problem during sending this.
Stay tune right here...
n u r u l ~~ A full cup must be carried steadily.
Sunday, August 26, 2007
Software Requirements Specification (SRS)?
An SRS is basically an organization's understanding
of a customer or potential client's system
requirements and dependencies at a particular point in
time prior to any actual design or development
work. It's a two-way insurance policy that assures that both
the client and the organization understand the other's
requirements from that perspective at a given point in
time.
The SRS document itself states in precise and explicit
language those functions and capabilities a software system
must provide, as well as states any required constraints by
which the system must abide. The SRS also functions as a
blueprint for completing a project with as little cost growth
as possible. The SRS is often referred to as the "parent"
document because all subsequent project management documents,
such as design specifications, statements of work, software
architecture specifications, testing and validation plans, and
documentation plans, are related to it.
It's important to note that an SRS contains functional and
nonfunctional requirements only, it doesn't offer design
suggestions, possible solutions to technology or business
issues, or any other information other than what the
development team understands the customer's system requirements
to be.
of a customer or potential client's system
requirements and dependencies at a particular point in
time prior to any actual design or development
work. It's a two-way insurance policy that assures that both
the client and the organization understand the other's
requirements from that perspective at a given point in
time.
The SRS document itself states in precise and explicit
language those functions and capabilities a software system
must provide, as well as states any required constraints by
which the system must abide. The SRS also functions as a
blueprint for completing a project with as little cost growth
as possible. The SRS is often referred to as the "parent"
document because all subsequent project management documents,
such as design specifications, statements of work, software
architecture specifications, testing and validation plans, and
documentation plans, are related to it.
It's important to note that an SRS contains functional and
nonfunctional requirements only, it doesn't offer design
suggestions, possible solutions to technology or business
issues, or any other information other than what the
development team understands the customer's system requirements
to be.
Wednesday, August 22, 2007
chapter 5
Assalamualaikum…
Hi guys..hope all of u are fine. Tomorrow we will start chapter 5. Before we start learn about this chapter, I want to share what this chapter means to us. In this chapter, we will look at what it means to design a system. The design begins at high level, with important decision about system architecture based on system requirement, desirable design attributes and the long-term intended use of the system. Hope this can help us to understand easier what is chapter 5 is about...
Hi guys..hope all of u are fine. Tomorrow we will start chapter 5. Before we start learn about this chapter, I want to share what this chapter means to us. In this chapter, we will look at what it means to design a system. The design begins at high level, with important decision about system architecture based on system requirement, desirable design attributes and the long-term intended use of the system. Hope this can help us to understand easier what is chapter 5 is about...
Tuesday, August 21, 2007
today..
hi..
In the beginning of the class, there was a problem with the projector and we need to call a technician to fix the problem. While waiting for the projector to be fixed, we did exercise on use-case diagram and state chart transition diagram.
After that, we finished chapter 4 today and it was so fast. We skipped certain slides and we only focus on important slides.
That’s all for today..
In the beginning of the class, there was a problem with the projector and we need to call a technician to fix the problem. While waiting for the projector to be fixed, we did exercise on use-case diagram and state chart transition diagram.
After that, we finished chapter 4 today and it was so fast. We skipped certain slides and we only focus on important slides.
That’s all for today..
Monday, August 20, 2007
Already
Assalamu'alaikum and hello everybody.
We are now in week 7, means we've gone through half of the semester. The spirit is not as high as in the erlier semester plus with a lot of assignments, quizzes and tests.
Wish you all a very good luck in tests.
We are now in week 7, means we've gone through half of the semester. The spirit is not as high as in the erlier semester plus with a lot of assignments, quizzes and tests.
Wish you all a very good luck in tests.
Saturday, August 18, 2007
What Kind of Information Should an SRS Include?
Several standards organizations (including the IEEE) have identified nine topics
that must be addressed when designing and writing an SRS:
1. Interfaces
2. Functional Capabilities
3. Performance Levels
4. Data Structures/Elements
5. Safety
6. Reliability
7. Security/Privacy
8. Quality
9. Constraints and Limitations
that must be addressed when designing and writing an SRS:
1. Interfaces
2. Functional Capabilities
3. Performance Levels
4. Data Structures/Elements
5. Safety
6. Reliability
7. Security/Privacy
8. Quality
9. Constraints and Limitations
Friday, August 17, 2007
Our Portal Progress (part 1)
Assalamualaikum
About our portal, I have looking for software to make it. One of the software is Joomla. It has verry good setting but its quite hard to used it. Maybe I should test it during my holliday. There are many more software that can be used to creat our portal. For more info you can visit its main site; http://www.joomla.org .If we using it, we must find some free hosting to upload our portal. This will be a good experience for our group. I will ask Lukman for his approval. That all for my reports.
About our portal, I have looking for software to make it. One of the software is Joomla. It has verry good setting but its quite hard to used it. Maybe I should test it during my holliday. There are many more software that can be used to creat our portal. For more info you can visit its main site; http://www.joomla.org .If we using it, we must find some free hosting to upload our portal. This will be a good experience for our group. I will ask Lukman for his approval. That all for my reports.
Thursday, August 16, 2007
requirement definition
Hello again..
For this time I just want to share about one of the kinds of requirements document. It is the requirement definition. It is a complete listing of everything the customer wants to achieve. This document express requirement by describing the entities in the environment in which the proposed system will be installed and by describing the desired constraint on, monitoring of, or transformation of those entity
For this time I just want to share about one of the kinds of requirements document. It is the requirement definition. It is a complete listing of everything the customer wants to achieve. This document express requirement by describing the entities in the environment in which the proposed system will be installed and by describing the desired constraint on, monitoring of, or transformation of those entity
Tuesday, August 14, 2007
SRS???
hi guys.. :)
As what Luqman mentioned in previous post, today we learnt about Software Requirement Specifications (SRS). Actually the objectives of this chapter are to elicitate requirements from the customers, modeling requirements, reviewing requirements to ensure their quality and documenting requirements for use by the design and test teams.
Besides, we also learnt about Use Case and the different between Data Flow Diagram (DFD). The different is DFD is more details compared to Use Case. I guess we will learn more about Chapter 4 in the next class. So, be prepared guys!
Pn. Badariah reminds us that we need to upload the completed SRS in our Blog latest Sept 9, 2007. As usual, late submission will be penalized.
Lastly, good luck to all my friends who gonna have exam this week.
Al-fatihah to Allahyarham Fadhil Ahmad..
As what Luqman mentioned in previous post, today we learnt about Software Requirement Specifications (SRS). Actually the objectives of this chapter are to elicitate requirements from the customers, modeling requirements, reviewing requirements to ensure their quality and documenting requirements for use by the design and test teams.
Besides, we also learnt about Use Case and the different between Data Flow Diagram (DFD). The different is DFD is more details compared to Use Case. I guess we will learn more about Chapter 4 in the next class. So, be prepared guys!
Pn. Badariah reminds us that we need to upload the completed SRS in our Blog latest Sept 9, 2007. As usual, late submission will be penalized.
Lastly, good luck to all my friends who gonna have exam this week.
Al-fatihah to Allahyarham Fadhil Ahmad..
Monday, August 13, 2007
Go Go Go ...
Assalamu'alaikum wbt and helo evrybody ..
Tomorrow we will continue lecture in chapter 4. This chapter is very important with respect to our project because it cantains the SRS.
So, it is very helpful to have everybody understand the concept well before we can run our project. It will become a burden if we drag it until the last minute because I hope we can impress Pn. Badariah once again by submit the SRS ASAP.
Luqman - Nurul, Ridhwan and Afiq, where's your post?
Tomorrow we will continue lecture in chapter 4. This chapter is very important with respect to our project because it cantains the SRS.
So, it is very helpful to have everybody understand the concept well before we can run our project. It will become a burden if we drag it until the last minute because I hope we can impress Pn. Badariah once again by submit the SRS ASAP.
Luqman - Nurul, Ridhwan and Afiq, where's your post?
Wednesday, August 8, 2007
why??
Hi guys…
Finally we can see our WBS here huhu…tomorrow we gonna have our SE class again. Hope that our lecturer, Pn.Badariah already fine because she got flu during our last class.. Owh we will start chapter 4 tomorrow. Hope all of us already read a little bit about the materials. Anyway I don’t understand even I’ve read the material before the class, I still can’t answer her question…Can somebody answer me?
Finally we can see our WBS here huhu…tomorrow we gonna have our SE class again. Hope that our lecturer, Pn.Badariah already fine because she got flu during our last class.. Owh we will start chapter 4 tomorrow. Hope all of us already read a little bit about the materials. Anyway I don’t understand even I’ve read the material before the class, I still can’t answer her question…Can somebody answer me?
Tuesday, August 7, 2007
Bad day..
Assalamualaikum..
The first 1 hour in the class, we learnt about chapter 3 and right after that Pn Badariah has viewed WBS from each group. By the way, Pn Badariah was not satisfied with WBS from each group.
Actually we are supposed to present our WBS, unfortunately we did not upload the WBS in our blog yet. So, we were penalized and Pn Badariah is going to deduct 1% of our marks. That was a mistake which should not happen. Never mind, we will take it as a lesson and we will try to work harder in future.
The first 1 hour in the class, we learnt about chapter 3 and right after that Pn Badariah has viewed WBS from each group. By the way, Pn Badariah was not satisfied with WBS from each group.
Actually we are supposed to present our WBS, unfortunately we did not upload the WBS in our blog yet. So, we were penalized and Pn Badariah is going to deduct 1% of our marks. That was a mistake which should not happen. Never mind, we will take it as a lesson and we will try to work harder in future.
Monday, August 6, 2007
Presentation
Assalamu'alaikum wbt and hai everybody ...
As you all know that we choosed the Waterfall model for our project. This model seems easy to understand, but actually it is a bit difficult to implement because a lot of research, study and homework must be done before it can be executed.
However, I think this will improve our understanding in this subject. To all c2d's member, especially the presenter, don't forget we have the WBS presentation tomorrow. I wish you luck and all the best ...
Luqman - Do your work with full spirit
As you all know that we choosed the Waterfall model for our project. This model seems easy to understand, but actually it is a bit difficult to implement because a lot of research, study and homework must be done before it can be executed.
However, I think this will improve our understanding in this subject. To all c2d's member, especially the presenter, don't forget we have the WBS presentation tomorrow. I wish you luck and all the best ...
Luqman - Do your work with full spirit
Saturday, August 4, 2007
The Attributes of Good Software
- The software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable.
- Maintainability - software must evolve to meet changing needs.
- Dependability -software must be trustworthy.
- Efficiency -software should not make wasteful of system resources.
- Usability - software must be usable by users for which it was designed.
Thursday, August 2, 2007
Smile and Smile... :D
Assalamualaikum and Hello everyone… (“,)
Today is 2nd August 2007 and now we are in the month of National Day. For today, we had 1 hour class with Puan Badariah and she has changed our class from BW-01-L06 to BW-01-L05 until the end of the semester, but she doesn’t state because of what.
We learnt about new topic which is Chapter 3 – Planning and Managing the Project.
Puan Badariah explained again about Work Breakdown Structure or more synonyms with name WBS.
After half an hour, Puan Badariah asks us to sit in group and come out with our Projects Phase, Steps and Activities. Puan Badariah gave us 15 minutes to discuss about it. But seems all the student doesn’t have enough time to discuss, Puan Badariah at last ask us to present it next week.
In addition, Puan Badariah gave the guideline how to come out with a good WBS and she explained the steps to get there.
That’s all for today activities.
Stay tuned for more information about Software Engineering course from my friends.
n u r u l ~~ Wait until it is night before saying that it has been a fine day.
Today is 2nd August 2007 and now we are in the month of National Day. For today, we had 1 hour class with Puan Badariah and she has changed our class from BW-01-L06 to BW-01-L05 until the end of the semester, but she doesn’t state because of what.
We learnt about new topic which is Chapter 3 – Planning and Managing the Project.
Puan Badariah explained again about Work Breakdown Structure or more synonyms with name WBS.
After half an hour, Puan Badariah asks us to sit in group and come out with our Projects Phase, Steps and Activities. Puan Badariah gave us 15 minutes to discuss about it. But seems all the student doesn’t have enough time to discuss, Puan Badariah at last ask us to present it next week.
In addition, Puan Badariah gave the guideline how to come out with a good WBS and she explained the steps to get there.
That’s all for today activities.
Stay tuned for more information about Software Engineering course from my friends.
n u r u l ~~ Wait until it is night before saying that it has been a fine day.
Wednesday, August 1, 2007
Juz some addition...
Bonjour…
Last 2 days we had our presentation, today we rest for a while then tomorrow we gonna have SE class again…well I think I just want to add some more information about our group because during the presentation Mr.Luqman forgot to tell us a few things..
These are some of the things that we didn’t said last day:-
Everyone of us responsible to post entry once a week so that all of us will take part on this blog.
This means we will have at least 6 entry per week.
We choose blue as our main colour is actually because when we entered at Pn.Badariah’s page, we see that she also use blue as her main colour, so we thought that she loves blue..but unfortunately Pn.Badariah’s page is actually green in colour. I don’t know how this can happen. Maybe technical error huhuhu…
That’s all…see you again
Last 2 days we had our presentation, today we rest for a while then tomorrow we gonna have SE class again…well I think I just want to add some more information about our group because during the presentation Mr.Luqman forgot to tell us a few things..
These are some of the things that we didn’t said last day:-
Everyone of us responsible to post entry once a week so that all of us will take part on this blog.
This means we will have at least 6 entry per week.
We choose blue as our main colour is actually because when we entered at Pn.Badariah’s page, we see that she also use blue as her main colour, so we thought that she loves blue..but unfortunately Pn.Badariah’s page is actually green in colour. I don’t know how this can happen. Maybe technical error huhuhu…
That’s all…see you again
Subscribe to:
Posts (Atom)
