What are the characteristics of a great Software Requirements Specification (SRS) ?

An SRS should be..

(1) Correct :
This is like motherhood and apple pie. Of course you want the specification to be correct. No one writes a specification that they know is incorrect. We like to say - "Correct and Ever Correcting." The discipline is keeping the specification up to date when you find things that are not correct.

(2) Unambiguous :
An SRS is unambiguous if, and only if, every requirement stated therein has only one interpretation. Again, easier said than done. Spending time on this area prior to releasing the SRS can be a waste of time. But as you find ambiguities - fix them.

(3) Complete :
A simple judge of this is that is should be all that is needed by the software designers to create the software.

(4) Consistent :
The SRS should be consistent within itself and consistent to its reference documents. If you call an input "Start and Stop" in one place, don't call it "Start/Stop" in another.

(5) Ranked for Importance :
Very often a new system has requirements that are really marketing wish lists. Some may not be achievable. It is useful provide this information in the SRS.

(6) Verifiable :
Don't put in requirements like - "It should provide the user a fast response." Another of my favorites is - "The system should never crash." Instead, provide a quantitative requirement like: "Every key stroke should provide a user response within 100 milliseconds."

(7) Modifiable :
Having the same requirement in more than one place may not be wrong - but tends to make the document not maintainable.

(8) Traceable :
Often, this is not important in a non-politicized environment. However, in most organizations, it is sometimes useful to connect the requirements in the SRS to a higher level document. Why do we need this requirement?

Today....

Thank you so much to our lecturer, Puan Badariah Solemon for teaching us today although she a little bit ill… We very appreciated to the effort that has been given by our lecturer and apologize because not able to answer to our lecturer question… These is because we are very hungry and our hard disk seems very slow today….... hehehehh

Lastly; we really appreciated and solute to our lecture and thank you so much…. Chayouk2 for CSEB233 ….. hehehe

p/s: girls; bring some candy to our class…. Then distributed among us ok… we take turns hahahahhaha…. Bring Cadbury to class hehehehheh

Chapter 4:Capturing requirement

Assalamualaikum and hello to everybody…

What have we learnt today? Requirement….

What is requirement?
According to Logman dictionary; Requirement means something that needed or asked for….
In software engineering; requirement means the something user’s needs. A requirement deal with; object or entities for example such as staff or student (in our database subject it might being referred to entities or table name), state they can be in and function that are performed to change the object characteristic.

Why requirement are very important?

Because if the requirement doesn’t satisfy the user’s needs; the project may confront failure… The top factors of project failure:
- Incomplete requirement
- Lack user requirement
- Unrealistic expectation
- Lack of executive support
- Changing requirement and specification
- Lack of planning
- System no longer needed

This can cause the organization suffered costly project and wasted the time of developing the system. For example; if a project has completed till the implementation phase suddenly the developer realized that the users/customers needs does not completed (Incomplete requirement). Therefore they needed redo all the phase from the start which is phase one; requirement and analysis .This will cause the organization to pay extra cost and wasted their time.

upgrade the blog

Assalamualaikum...
Today we upgrade the blog such as categorize the post..uplode the pictures..arrange the page and many more....
we want our blog very interactive and nice blog...
thank you girls...

WBS

Girls, here is our WBS;



if you want to download it; visit:

WBS1.doc

Have a nice day!!!

Beginning of Chapter 4

Assalamualaikum and good morning...

Today we have started learning chapter 4...Capturing the Requirements...
We learnt about the Requirement process...
A requirement is an expression of desired behaviour. Requirement deals with objects or entities, the state they can be in and functions that are performed to change states or object characterics...
Requirements focus on the customer needs, not the solution or implementation...

We will continue Chapter 4 in our next lecture...

By the way..start from this chapter, we will start to produce our Software Requirements Specification (SRS)..

Thank you...

Gantt Chart ?

A Gantt chart is a graphical representation of the duration of tasks against the progression of time. It is a useful tool for planning and scheduling projects. A Gantt chart also helpful when monitoring a project's progress. From the Planning and Scheduling perspective, Gantt Chart allows you to assess how long a project should take. It is lays out the order in which tasks need to be carried out and helps manage the dependencies between tasks.

Example :

Extra information for WBS

A Work Breakdown Structure (WBS) is a fundamental project management technique for defining and organizing the total scope of a project, using a hierarchical tree structure. The first two levels of the WBS (the root node and Level 2) define a set of planned outcomes that collectively and exclusively represent 100% of the project scope. At each subsequent level, the children of a parent node collectively and exclusively represent 100% of the scope of their parent node. A well-designed WBS describes planned outcomes instead of planned actions. Outcomes are the desired ends of the project, and can be predicted accurately; actions comprise the project plan and may be difficult to predict accurately. A well-designed WBS makes it easy to assign any project activity to one and only one terminal element of the WBS.

just read it girls.....

User Requirement Specification

Objective

The purpose of this work is to ascertain and record the users’ requirements for an EDM / workflow system. The document produced includes details of the existing and proposed IT infrastructure and business practices.
It is recommended that the process includes a high level view of the information requirements and document handling patterns of the whole organisation in addition to a detailed study of the area(s) chosen for the pilot(s). The process may take place in two stages, with the high level study being concluded in advance of a decision on the area(s) for the detailed study. In this case, the client may decide if an interim report is required.
The User Requirement Specification (URS) is constructed in such a way that it can be used as the basis from which to develop an Invitation to Tender (ITT) as part of the procurement exercise for a system to meet the client's needs. It is an internally focussed document, including discussion of options and explanation of technical processes for reference as appropriate / requested.

Method

Designated people from the relevant areas are interviewed. Notes of the interviews are produced and fed back to the interviewees for agreement. The existing IT infrastructure are documented as needed, together with any plans for upgrading and any impact of an EDM system on these proposals. The outcome of these processes are written up in a User Requirement Specification. This is circulated in draft form for comment and then issued as a final document.

What happen to our WBS?

Assalamualaikum and good evening...

Today we had our Work Breakdown Structure(WBS) presentation.We would like to apologise to our lecturer,Pn. Badariah because we cannot show our WBS. We had uploaded our WBS in the blog, but..during Pn.Badariah tried to open the link to our WBS document..however 'server not found' was stated. After our class, we went to the lab to try to open the link again, we managed to open the link and see the WBS document..we succeed. We are not sure why the link cannot be open in class. May be there's something wrong with the computer in our class.

WBS uploader

Girls... here are the links to our new WBS..... hehehehhe

WBS2.doc

WBS again..

Hello everyone...

Tomorrow we have to present our Work Breakdown Structure in the class...
Pn. Badariah told us to upload our WBS in the blog...

InsyaAllah this evening we will upload it....:)

Hope to see all of you tomorrow...
We will continue with chapter 3 tomorrow...so, be prepared before you guys come to class...

Adioss...