Catering Staff Management

Key Requirements:

To develop a web application for an employment agency for managing catering staff and placing order by the customers.

Technology Used:

Software/Tool:

Platform:
Windows
Linux

Key Features Our Role:

We are working on the web application as a business process consulting and development partner. Continuous enhancements are made to the application as the business progresses or changes. We understand business, design solution, construct and also maintain the web-application.

Process Implementation Step

Our matured SDLC process (that is an ISO 9001:2000 certified process) assists us in continuously improving the application and maintain it to deliver business functions.

We provide business process consulting to our client to identify the best and cost effective technology solution that meets short term and long term objectives. These projects are defined in the form of SRS and developed using our structured SDLC.

S.No.	Name	Purpose	Inputs	Outputs
1.	Project Initiation	To identify resources (including PM), communication mode, frequency and have internal meeting with the team and kick-off meeting with the client.	Project sign off, documents, pre-sales estimation and client information.	Minutes of internal meeting and kick-off meeting
2.	Project Planning and Estimation	To do detailed estimation to cover all requirements and risks and make the project plan	Initial Requirement documents	Detailed project plan that contains details of tasks, time allocation, resources, deliverables, delivery and milestones.
3.	Project Monitoring and control	To monitor the project and provide flags to the health of the project on regular basis.	Project Plan and previous week project status.	Weekly project status report and Minutes of meeting of project status review meeting.
4.	Requirement Management and Requirement Development	To define process for requirement gathering, collect requirements, prepare SRS to contain both functional and non-functional requirements, get it approved from the client and prepare the Requirement Traceability Matrix to trace all change requests. Issues are traced to closure using bug tracking tool.	Project documents	SRS, Requirement Traceability Matrix
5.	Design	To prepare the design and architecture of the system	SRS document	Design document and design review
6.	Coding	To code a module/release based on architecture design. QA independently writes test cases	SRS, design documents and unit testing test cases	Source code, release on staging to QA, test cases
7.	Testing and Review	Review is done for all necessary tasks during project execution: Requirement analysis review, design/architectural review, code review, test cases and test plan review. To test the release based on the requirements.	SRS, design documents, source code	Source code, release on staging to QA, test review
8.	Configuration Management	To ensure system and software configuration create version control repository, create project account in bug tracking tool and constitute change control board.	Minutes of Kick off Meeting, Change requests	CVS Repository, BTS account

Process Implementation Step

Process Implementation Step

Schedule variance = (Planned schedule - Actual Schedule)/Planned schedule X100

	Estimated time ( in working days)	Actual time (in working days)	Variance (% Change)
SRS	3	4	33.33
Layout Design	4	6	50
Database design	3	3	0
Construction	20	21	5
Testing	10	10	0
Release	5	3	-40
	45	47	4.44

**The effort information is representative only to protect the confidentiality.

Planned Schedule (Taken from Microsoft Project Plan) = 61 calendar days Actual Schedule (Taken from Weekly Status Reports) = 65 calendar days Schedule Variance = (65-61)/61X100= 6.56%

Effort Variance

Formula Used

Effort variance = (Planned effort - Actual effort)/Planned effort X100

	planned effort (in no. of person hours)	Actual effort (in no. of person hours)	Variance (% Change)
SRS	24	40	66.67
Layout Design	32	54	68.75
Database design	24	27	12.5
Construction	160	168	5
Testing	80	80	0
Release	40	24	-40
	360	393	9.17

**The effort information is representative only to protect the confidentiality.

Note: The planned effort was calculated based on the assumption that there are 8 working hours in a day.