phase-I

 

 

 

Introduction

 

    Our world is evolving around us, new technology is being created everyday so we need something new.Something easy to work with, so that is why  KSU decided to create a new system, this system is designed to help a lot of people and tomake life easier. It’s main goal is to produce a well studied project presentation schedule online instead of manually as before. It’s about organizing the grad students and staff schedules to obtain an emp slot for the project presentation time, any preferences or exclusions on any side can be updated online instead of face to face or by email which may cause errors, this is a web-based system designed with prototype model,  this system alsoprovides tow main functions:

 

            1. Account Managing and Maintenance:

 

a)  Create and update account:   the user can create and update his/her account.

                           Account contains user’s information such that Group name and ID, user name and ID, email, schedule.

b)     Login: to be able to use his/her account the user must login.

c)     Logout: to sign out providing more security.

d)    Contact: allow the user to contact with website administrator via e-mails.

   2. Schedules Managing and Maintenance :

 

a)     Add schedule:  the user can add his/her schedule.

b)     Edit schedule:  the user can update his/her schedule.

c)     Delete schedule:  the user can delete his/her schedule.

 

 Functions for specific users

Administrator:

a)       Delete accounts: the administrator may delete accounts.

b)       Notify users: the administrator can notify intended users

c)Delete Archive: the administrator maydelete the Archived users or groups when the information is not needed any more.

 

To decided the most appropriate software development approach with the given constraints, constraints, this is all models we though t about,but they were not exeptable for the following reasons: in the  waterfall approach , the activities will represents as separate process , which is difficult to respond to changing customer requirements  while we don't  understood all requirements, and we can't see any functionality until end of the project , In Exploratory approach, there is no  functionality in early because it's depend on documentation, while in incremental some of system functionality is available earlier but the requirement  must be clear and well understood , because it's depend on prioritised of requirements,the spiral approach is for large, expensive and complicated system and our system is small and we don't need this approch, while The CBSE approach based on systematic reuse where systems are integrated from existing component or COTS system, this approach is perfect because it’s reduce costs and risks and it’s be faster delivery so it’s appropriate in this side ,but in this system we don't  understand all requirements and may be the system dose not meet real needs of users and we can’t  change any code cause it’s has copywriter.. at  the end this approach is not an appropriate  model .last..Prototype model :this approach is a best model cause it’s appropriate for our system in many reason. First, the customer want the system early so the prototype may can we start work in the first phase in the project so present some of functionality early. Also we didn’t understand all requirement, the customer define a general objective for the software but they dose not identify detailed input , processing ,or output requirement . and if the customer know exact what he want we can do it in any phase comfortably, For these reason we have chosen the prototype model is the best for our system...

 

 

 

Team Organization

 

 since this is a small system it will be consist of only 12 member

 

Member name	ID	E-mail
Ramah   AL-Balawi **Leader**	424200300	ramah-ksu@hotmail.com
Bashear AL-Khwatier	425202048	bkhwaiter@hotmail.com
Bedour  Abouammoh	425201536	b.abouammoh@yahoo.com
Dania Alomar	424202273	sunlife_11122@hotmail.com
Lamya AL-Jasser	425203811	lavender-l@hotmail.com
Mada AL-Haidary	425202309	Mada_ksu@hotmail.com
Rana AL-Rasheed	42420 2201	rnoon-abs@hotmail.com
Sara AL-Mis-her	425202738	daffyduck_sara@hotmail.com
Tamam AL-Ayed	425200594	patchi_66@hotmail.com
Najd Al-mouh	424201216	a7la_najd@hotmail.com
nouf Al-Ajmi	425200325	na.alajmi@hotmail.com
nouf alghanmi	425200207	nlof@hotmail.com

 

 

Risk Management:

Risk represents uncertainty.

 

 

 

The more uncertainty there is in an activity the greater the difficult it will be towards a successful completion.

 

 

It is fair to say that anything that can

affect the performance of the product wouldconstitute a risk .  However, this event would need to be uncertain and have asignificant impact.

When something goes wrong and there is no 'plan' in place to tackle it you are intocrisis management. It's possible that you may get away with this on occasion but regular crisis management will cause a lot of problems

 

The impact of a risk, should it occur, will be to jeopardize the project's ability to succeed at one of its objectives.

 

High risks that should be resolved in the baseline plan.  The best managers should be assigned. Additional resources should be applied.  With some of these risks, project descoping might be considered.

 

Moderate risks that can be addressed with plans that balance the cost of risk management with the risk-adjusted impact on the project. Contingency plans can be applied to these risks.

 

Low risks,which can often be left to the project team to address as they arise during the project.

 

Risk Analysis schedule:

 

 

 

No.	Type	Risk Factor	Impact Qualification (L,M,H)	Probability  Qualificaion (L.M.H)
1     2     3     4	Client	Input wrong data from the user User fail to understand the impact of requirements changes. Narrow knowledge level of users Absence level of commitment level of users	H L     M      M	H L M    L
4 5 6 7	Staffing	Team lateness because of exams and other assignments Number of team members unknowledgeable of project Team members working together as a group for the first time Physical location of team members prevents effective management	L  M   H   M	H   L M M
8 9 10 11	Technical	Internet and connection problems   The database used in the system cannot process as many transactions per second as expected.   Sceurity problems like hackers and malicious access the site   Project size in comparison to timeline Resource availability is inconsistent	M  H H L	M  L M L

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

A strategy to manage that risk:

 

 

Add a link that contains the steps of dealing with the site and add link a n e-mail address to reply the user questions.	User fail to understand the impact of requirements	Risk avoidance Strategy
Reorganize team so that there is more overlap of work and people from different level who doesn’t have exams. to understand each other’s job.	Team lateness	Minimization strategy
Make sure that the user understands how it is important to upload his own data and keep trying until the connection problem fixed ,or the pressure on the database that may caused the problem  is fixed too . build a firewall to protect the site.	Internet and connection problems + Database problems +Sceurity problems	Contingency plan

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Work Breakdown

 

No.	Task	Milestones	Timing
1	Develop the project plan	plan report(Milestones)	March 14-21,2008
2	Develop the SRS document	SRS Documentation (Deliverables)	March-April 22-11,2008
3	Software Design	Architecture Design(Milestones)	April-May 12-2,2008
4	Implementation and Testing	Validation Documentation(Milestones)	May 3-16,2008
5	System Evolution	Evolution Report(Milestones)	May-June 17-6,2008

 

 

 

Project Schedule

 

Task duration and Dependency

 

 

 

Task NO.	Activity	Duration(dayS)	Dependencies
	SW Development
T1	-Determine the project scope	2days	-----
T2	-Gther information	1day	-----
T3	-Develop project plane	5days	T1/T2
T4	-Determine system functionality and project requirement	3days	T1/T2
T5	-Develop SRS Documentation	7days	T4
	Software Analysis and Design
T6	-Analysis and Design Data Base	5days	T5
T7	-Analyze and Design slot selection algorithm	5days	T5
T8	-Analyze and Design registration method	3days	T5
T9	-Analyze and Design   schedule import method	2days	T6
T10	-Analyze and Design schedule update method	2days	T6
T11	-Analyze and Design design search function	1day	T5
T12	-Analyze and Design design privacy policy	3days	T5
	Software implementation and unit test
T13	-Implement and unit test Data Base	2days	T6
T14	-Implement and unit test slot selection algorithm	2days	T7
T15	-Implement and unit test registration method	1day	T8
T16	-Implementand unit test schedule import method	1day	T9
T17	-Implement and unit test schedule update method	1day	T10
T18	-Implement and unit test search function	1day	T11
T19	-Implement and unit test  privacy policy	1day	T12
	Integration time
T20	-Integrat the project parts	2days	from T13 until T19
	Project test
T21	-Test all project part	2days	T20
	Final version
T22	-Develop Evolution report	1day	T21
	Evolution time

 

 Activity Network  :

Network.mpp 

 

Activity Bar Chart :

Bar_Chart.mpp  

                       

 

 

Monitoring and Reporting Mechanisms 

 

Any plan needs to be monitored to ensure that it progresses towards its intended outcomes. This ensures efficient management of the project and provides a means to communicate initiatives and achievements. For that reason the PSS Project uses a participatory review approach( teamwork meeting and communication) to monitor the progress of the project activities against predefined objectives.

 

 The strategy is:

 

Weekly Meeting: each phase has at least one faca-to-face metting, as for:

*  sharing the general idea in this phase between teamwork members.

* Discussion previous step and its results.

* Discussion what will be done.

 

During a week:Teamwork have to keep communicating  each other and document their decisions to be add to the next meeting report.

Communicating is done by : No Pain No Gain Online Wiki (http://nopainnogain.pbwiki.com/), Email and Cellphone.

 

 

Reporting time table

 

NO.	Timing	Reporting /Monitoring (main Idea)
1	March 14-19,2008	Report heading: 1.Teamwork members information and their schedules
2	March 17-19,2008	Report heading: 2. Project Plan
3	March 22-28,2008	Report: 3. About current status
4	March-April 29-4,2008	Prototype version 1
5	April 5-11,2008	Report heading: 5. SRS Document
6	April 12-18,2008	Prototype version 2
7	April 19-25,2008	Report heading: 6. final modifications on prototype version 2
8	April- May 26-2,2008	Prototype version 3
9	May 3-9,2008	Report heading: 7.Designing Report
10	May 10-16,2008	Report: 8. About current status
11	May 17-23,2008	Report heading: 9.Implemintion Report
12	May 24-30,2008	Report: 10. About current status
13	May-June 31-6,2008	Report heading: 9.Evolution Report