Work Breakdown Structure

Assalamualaikum...

Today, Pn. Badariah tought us part of chapter 3 about Planning and Managing the Project...
After about 3o minutes of lecture, we were required to sit in our own group to discuss and start doing the Work Breakdown Structure (WBS) for our project.

All of us were there, except Mumtaz... If i'm not mistaken, she was not feeling well...

Anyway, back to the group discussion...
The purpose of doing the WBS is to separate the project development into a succession of phases which are composed of steps, which are composed of activities...

WBS describes the software-development cycle for a particular project by enumerating te phases or stages of the project and breaking each into discrete tasks or activities to be done. Besides that, the WBS potrays the interactions among these activities and estimates the time that each task or activity will take. Therefore, we can say that the WBS is a timeline that shows when activities will begin and end, and when the related development products will be ready.

According to Pn. Badariah, we are required to show our WBS on our next class which is on Tuesday...

Anyway, we are still working on our schedule. We didn't manage to finish it during class...

That's all...

What is a Software Requirements Specification (SRS)

An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point intime (usually) prior to any actual design or developmentwork. It's a two-way insurance policy that assures that boththe client and the organization understand the other'srequirements from that perspective at a given point intime.

The SRS document itself states in precise and explicitlanguage those functions and capabilities a software system(i.e., a software application, an eCommerce Web site, and soon) must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blue print for completing a project with as little cost growt has 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.

First Presentation

Assalamualaikum and good evening.....

Today we had our first presentation in the class...
We had no lecture...but, all groups were required to present their blogs...
We were the last group to present....

First of all... I would like to apologise to my group members...
The presentation didn't go well as we planned...
Perhaps because I was not fully prepared...and kindda nervous...
I'm sorry... I hope that I will do better in the future...:)

I would like to congratulate some of my friends who did well in their presentations.
Some of them presented very well.

We were required to present everything about the blog... from the reason we choose blogspot...up to the job distribution among the team members.
As I said during the presentation, all of us are free to update the posts anytime as we want to...
This is because, some of us might have no internet access at times, or busy with assignments and classes...therefore, anyone who is free can update the post. We did not specify the day for each of us to update the post... Anyone can update the post at anytime.

Anyway...I'm sorry because I didn't mention the right number of the post we had uploaded during the presentation this afternoon... Actually...we had uploaded 23 posts at that time...not 29 posts... I'm sorry for that... Maybe I was confused during the presentation... I just totally forgot everything....huhuhu....

I just hope that I'll be fully prepared for the second presentation...
I must say that I had learn a lesson from the first presentation and I hope that I wont repeat the same mistake...

A sample of a basic SRS outline

1. Introduction
1.1 Purpose
1.2 Document conventions
1.3 Intended audience
1.4 Additional information
1.5 Contact information/SRS team members
1.6 References

2. Overall Description
2.1 Product perspective
2.2 Product functions
2.3 User classes and characteristics
2.4 Operating environment
2.5 User environment
2.6 Design/implementation constraints
2.7 Assumptions and dependencies

3. External Interface Requirements
3.1 User interfaces
3.2 Hardware interfaces
3.3 Software interfaces
3.4 Communication protocols and interfaces

4. System Features
4.1 System feature A
4.1.1 Description and priority
4.1.2 Action/result
4.1.3 Functional requirements
4.2 System feature B

5. Other Nonfunctional Requirements
5.1 Performance requirements
5.2 Safety requirements
5.3 Security requirements
5.4 Software quality attributes
5.5 Project documentation
5.6 User documentation

6. Other Requirements
Appendix A: Terminology/Glossary/Definitions list
Appendix B: To be determined

Upcoming Topic

Chapter 2

• 2.3 Tools and Techniques for Process Modelling

Static Modelling

Dynamic Modelling

• 2.4 Practical Process Modeling Marvel Case Studies

Marvel Case Studies

Examples of Marvel Commands

Desirable Properties of Process Modeling

• 2.5 Information System Example

Piccadilly System

Lai Artifact Table for Piccadilly System

• 2.6 Real Time Example

Ariane-5 Software

update activities(picture)

assalamualaikum everybody..finally i upload the picture.

meeting or discussion at 26 july 2007...

group members

Laila Hana,Wawa,Wani,Baizura,Nano and Mumtaz

thank you girls...

Presentation 1

Assalamualaikum....

We'll be having our first presentation tomorrow...
huhuhu....
I hope that everything will go well...

Girls...make sure you come to class tomorrow...and don't be late.....

For tomorrow's presentation, we are required to present everthing about our blog... including the job distribution among us...

Okay...good luck everyone..
See you guys tomorrow....

Project

Assalamualaikum and good morning...

Project

About the project, we are required to produce a portal for this subject, Software Engineering. The client to this project is our lecturer, Puan Badariah. All of the requirements must be collected, analyzed, validated and documented properly from the client using methods and techniques that we learn in class. Minimally, the portal should contain the following:

• About the subject.
• Lecturer's info.
• Information related to a particular semester (also archive of information from past semesters, if any).
• Teaching/learning materials such as notes, slides etc.
• Assignments (also archive of past assignments, if any) page, inclusive of links to current student's blogs.
• Ease future maintenance, and has professional interface.
• Others that will make the portal complete and excellent.

The Deliverables

1. Assignment 1: Create a blog of group's activities throughout the project this semester.

2. Presentation 1: Present everything about the blog including job distributions among the team members.

3. Assignment 2: Produce SRS.

4. Assignment 3: Development and Delivery of Portal.

5. Presentation 2: The completed portal will be presented.

Comparison of Sofware Process Model (PART 3)

Girls; here summarized all of the software process model... hope this will help u all remember the important term(PART 3):

COMPARISON OF SOFTWARE PROCESS MODEL

AGILE MODEL
Pair programming (more on programming) *These method not being used nowadays because of critically time for market.

Comparison of Software Process Model (PART 2)

Girls; here summarized all of the software process model... hope this will help u all remember the important term(PART 2):

COMPARISON OF SOFTWARE PROCESS MODEL

OPERATIONAL SPECIFICATION MODEL	TRANSFORMATIONAL MODEL	SPIRAL MODEL
Detail up the program specification (coding) and try to execute.	Suitable for developing critical system (which definitely more complex because related to human life, environment, economic etc.	The only model that include the risk taking management (RTM)

Comparison of Software Process Model (PART 1)

Girls; here summarized all of the software process model... hope this will help u all remember the important term(PART 1):

COMPARISON OF SOFTWARE PROCESS MODEL

WATERFALL MODEL	PROTOTYPING	V MODEL
Document driven model Developer need full requirement and understanding to build the product. User should wait in a long time before the final product being release. without iteration	Developer need minimum requirement to build the product. User involved in the beginning of the developmentof the product.	Iteration from one phase to another.