final report group3

9
Final Report Gauravkumar Patel Darshankumar Patel Ankit Patel Rachit Pandya RedefineU Inc. (Team RacDarGauAnk) 1. Introduction 1.1 Overview Recreation Club Management System: In this system we are going to develop website which provides the functionality about different activity of recreation club. Manage membership and provide the timetable management features for members. 1.2 Deliverables Project Deliverables: 1. Website 2. SQL server database 3. Final project report Following is the list of deliverables throughout the project development: 1. Letter of Intent 2. Initial project plan 3. Weekly status reports 4. Gantt charts 5. Individual time sheets with burnt down chart 1.3 Assumptions and Constraints Assumption: Your desktop/Laptop or Mobile should have web browser. It should have Internet access. Constraint

Upload: gaurav-patel

Post on 26-Sep-2015

228 views

Category:

Documents


1 download

DESCRIPTION

Software Development SRS

TRANSCRIPT

Final Report

Gauravkumar PatelDarshankumar PatelAnkit PatelRachit Pandya

RedefineU Inc. (Team RacDarGauAnk)

1. Introduction 1.1 Overview Recreation Club Management System:In this system we are going to develop website which provides the functionality about different activity of recreation club. Manage membership and provide the timetable management features for members.

1.2 Deliverables

Project Deliverables:1. Website2. SQL server database3. Final project report

Following is the list of deliverables throughout the project development:1. Letter of Intent2. Initial project plan3. Weekly status reports4. Gantt charts5. Individual time sheets with burnt down chart

1.3 Assumptions and Constraints Assumption:Your desktop/Laptop or Mobile should have web browser.It should have Internet access.

ConstraintIt should support HTML4 or later version.

1.4 Risks and Assets Risks are as follows:Technical difficulties in installing or updating the softwares.Unavailability of developers.Deadlock condition Difficulties in learning new technology

Assets are as follows:DeveloperDatabase ManagerTesterDevicesInternet accessability.

2. Management Structure2.1 Project Life Cycle: Project will be done using agile scrum methodology.

2.2 Project Organization: Gauravkumar Patel is a scrum master. He is responsible for all project activity.Rachit Pandya is a developer. He will do front end/back end development work for projectDarshankumar Patel is a developer. He will be responsible for front end/back end development work.Ankit Patel is responsible for database and testing procedure for project.

2.3 Risk Management Plan:Project Manager and developers and all stakeholders who are involved in project, will take care all risk associated with project which are exist or may be arise in future. Risk will be recognized and solved as early as possible. There is surety by team that all risks will be handled so there is as much as less impact of it in project.Risk will be identified and assessed to come up with possible outcomes. Risk will be categorized as per top and bottom line risks.Risks will be responded as per following structure:Solve: Come up with ways to handle risksAvoid: remove risks by removing its root cause.Accept: Risk cannot be cure. It will be leave as it is.

2.4 Issue Management Issues is thing which is totally unexpected and it arises suddenly. For taking care of all issues we have framework for dealing it. It will help after identifying issues that what to do with it.1. Any issues regarding web design will be handled by Rachit Pandya.2. Issues regarding development problem will be handled by Darshankumar Patel.3. Issues regarding database and testing will be taken care by Ankit Patel.4. Any project requirements or development methodology and assignment of task related issues will be handled by Gaurav Patel.

2.5 Communications Project team will member will be constantly in touch with email conversation. We will have a meeting two times in a week. If there will be something urgent communication will be require then online video conferencing will be held.

As a team we decided to gather on every Wednesday to discussed and develop the project.We can meet at college library or at our apartment (as most of the team members are live in same apartment-20 Tuxedo Crt)

Methodology Our team is going to use Agile scrum Methodology. To develop our website we will use visual studio 2013, SQL server database as database development tool. On every Wednesday 6:30 p.m. to 8:30 p.m. we will have scrum meeting with all the team members at our home (20-Tuxedo court, as all the team members are roommates). We will also use library room for some important meetings. For source and version control we will going to use GitHub. There are four members in our team. 1 scrum master-Gaurav 3 Developers-Rachit, Darshan, Ankit Possible user for our website are: Members of our club, Admin/Management Person, Visitors.

Iteration Planning

Iteration-1 Velocity: User Story: As a user, I want home page to select services provided by system.

TaskDeveloperEstimateActual

Create Master page & Home PageD.P.1.0

Create Links and MenuR.P0.75

Design CSS PageA.P0.75

TestA.P0.25

User Story: As an admin, I can authenticate in my account.TaskDeveloperEstimate Actual

Create User InterfaceR.P0.5

Create and Design Database TableA.P0.25

Create Connection and Check AuthenticationA.P0.5

Test R.P0.10

User Story: As an admin, I can add/delete/update services.TaskDeveloperEstimate Actual

CreateUI pageR.P0.5

Add/delete/Update servicesD.P0.5

Change values in DatabaseD.P1.0

TestD.P0.10

User Story: As an admin, I can manage service calendar (ex.time schedule)

TaskDeveloperEstimate Actual

Create UI pageR.P1.00

Setup ConnectionA.P0.50

Business Login for reflected changesA.P0.50

TestD.P0.25

Use cases:

Possible use cases for our systems are: Subscription activity Un-Subscription activity Inquiry Calendar management Payment Login Account management Validation

Detailed Grant Chart Report

Use Case Diagram

ER Diagram

Test Case

ID1

TitleCheck Event Date

Pre-ConditionEvent must have upcoming date

Test StepCheck Date

Expected ResultIt allow to create Event

ID2

TitleAvoid Activities Confliction

Pre-ConditionEvent date available

Test StepCheck two or more event not at same time

Expected ResultAllow to Subscribe

ID3

TitleValidate Email

Pre-ConditionEmail Entered

Test StepCheck Email Validity

Expected ResultAllow to register

ID4

TitleValidate Any Space Available For new person

Pre-ConditionPerson must be registered

Test StepCheck number of participant for particular event

Expected ResultAllow to register for event

ID5

TitleMember paid his/her fees

Pre-ConditionMember must be registered.

Test StepBy entering billing ID it will confirm payment

Expected ResultAllow to attend activity