Vous êtes sur la page 1sur 7

Stephanie Chaney

Assignment B Brief Synopsis:

ISDS 4113

November 27, 2013

Arnold and Maria Starks own a fitness center in Cocoa Beach, Florida that offers its members fitness courses, fitness supplies, and an exercise gymnasium. Over the life of their business, the paperwork and administrative requirements have grown exponentially. As a result, they requested that a database be set up on their network to handle their day-to-day operations and transactions. Specifically, their database needs include push button access to reports, queries, and forms. The system should give the management and staff the ability to keep their business processes accurate, reliable, enforceable, and simple. In addition, Arnold and Maria want to use the information from the database for marketing requirements and for tracking purchases, orders, memberships, employees, and courses. As well, the Starks and the employees must be trained to use the new database. This project should not last longer than 30-40 days and will be completed by students. The only costs involved are those used for the documentation, training materials, and an installation portable disc drive. The database will not be used for payroll.

The setup requirements are as follows:

Employee:

Courses:

Legal name and birthdate Address and telephone number Position, hire date Employment status 4-digit employee number Company email address Qualification information

Instructor qualifications tracking Course lists of available courses, durations, and levels Course description, length, start date/times, and end date/times Class lists of members assigned to courses A three letter, three number course code

Merchandise: Members: Vendor information with 2-digit vendor code Vendor order information with receiving information Customer purchases with 7-digit transaction number Inventory information Printable order forms and purchase invoices Legal name, birthdate, gender Address and telephone number Membership - type, fees, status, and discounts Join date and membership status 6-digit member number

1|Page

Stephanie Chaney
Scope Statement Project: Health Club Database Project Objective

ISDS 4113

November 27, 2013

To program a centralized, multiuser database to be used for the day-to-day operations of a health club as a student project at no charge other than copies and a disc drive within one month. Milestones Establish and finalize project scope Complete team selection and team charter Completed database design Determine final budget requirements Establish project network and duration Complete MS Project input with project management of schedule/costs Develop risk management with contingencies Finish testing phase Completed programming of database Delivery to client Initiate training Complete documentation Review project 1/29/2014 1/30/2014 2/1/2014 2/11/2014 2/13/2014 2/13/2014 2/14/2014 2/17/2014 2/18/2014 2/19/2014 2/24/2014 2/24/2014 2/27/2014

Technical Requirements 1. 2. 3. 4. A working database will be installed on one Microsoft SQL Server and up to 10 computers connected to the network will be given access to the database. The database should allow multiple users The database should allow multiple users to enter data at the same time Printing will be done through a network printer for all outputs.

Limits and Exclusions 1. 2. No accounting function other than customer purchases and vendor orders are to be added Employee information is for information and scheduling of classes only. No human resource processes will be necessary and no payroll information is necessary. 3. Colors and fonts will be chosen by the owners before programming begins. 4. Any additional requirements will be assessed and charged after approval of the owners if not within this scope statement. 5. The company will be given one prototype delivery and allowed to test the system. After which, feedback will be collected and changes will be made according to the specifications and limitations of this scope statement. 6. After the prototype evaluation period, the final install will be made and at this time no other programming will be done. A new quotation and delivery process will be required. 7. The company will have a period of 30 days to report any bugs or glitches to the system after final delivery. 8. Work will be done between the hours of 3:00PM and 8:00PM Monday - Saturday. 9. The cost of printing the database documentation, training documentation, and an external portable disc drive are the only costs incurred. 10. The company id responsible to provide the appropriate network, printer, and computers at the job site. 11. There will be no overtime paid. Customer Review Owner of Health Club

2|Page

Stephanie Chaney
Project Priority Matrix

ISDS 4113

November 27, 2013

Time Constrain Enhance Accept

Performance

Cost

X X X

3|Page

Stephanie Chaney
Work Breakdown Structure

ISDS 4113

November 27, 2013

1.

2.

3.

4.

5.

6.

7.

8.

Assignment B Project - Database Design Project - schane1 Establish Project Scope 1.1. Needs Assessment 1.1.1. Meetings and Interviews 1.1.2. Meet with owners to discuss database needs, establish deliverables, and database use objectives 1.1.3. Obtain policies and procedure documents relevant to the database requirements 1.1.4. Review business rules of the company 1.1.5. Interview relevant staff and management to discuss policies and procedures to verify understanding 1.1.6. Scope Development 1.1.7. Assess available resources 1.1.8. Outline project technical requirements and database specifications 1.1.9. Form limits and exclusions 1.1.10. Write scope document 1.1.11. Review scope document with the owners of Fit4Life for approval Team Selection and Team Charter 2.1. Interview team members to form the team 2.2. Discuss project scope with team members 2.3. Create a team charter that outlines expectations and work ethic baselines 2.4. Appoint a Lead Programmer 2.5. Get team charter signed by all team members Budget Requirements 3.1. Get an estimation of the project time and cost from team based on their experience and previous programming jobs using an combination of the consensus method and function point method 3.2. Determine the function points 3.2.1. Inputs - tables and forms 3.2.2. Outputs - reports and queries 3.3. Complete budget worksheet estimating cost and number of programming hours required at each function point 3.4. Get client approval of budget Project Network and Duration 4.1. Have team develop a WBS and give node durations - establishing team by-in for deadlines later on after the final project network and total duration is finalized 4.2. Create project network to determine total project duration using MS Projects 4.3. Review WBS, project network, and total project duration estimate with the team 4.4. Get client approval for duration Risk Management 5.1. Obtain from team possible risks, their impact, likelihood, and controllability 5.2. Brainstorm how to mitigate, avoid, transfer, or retain risks 5.3. Develop a contingency plan Project Management of Schedule and Costs 6.1. Create a MS Project file to manage project 6.1.1. Import the WBS 6.1.2. Input Resources and costs 6.1.3. Establish precedence 6.1.4. Invite team to share the MS Project file through SharePoint for team communication and tracking of project Database Design 7.1. Create Entity-Relational diagram with minimums and maximums based on business rules 7.2. Write table names with preliminary attributes 7.3. Establish Primary and Foreign keys relationships 7.4. Check ER diagram with client Programming of Database 8.1. Create Tables, Validation Rules, Default Values, and Relationships 8.1.1. Table: Qualification 8.1.2. Table: EmployeeQual 8.1.3. Table: Employee 8.1.4. Table: Position

4|Page

Stephanie Chaney

ISDS 4113

November 27, 2013

8.1.5. Table: States 8.1.6. Table: Member 8.1.7. Table: FloridaCities 8.1.8. Table: Membership 8.1.9. Table: Course 8.1.10. Table: Merchandise 8.1.11. Table: Vendor 8.1.12. Table: VendorOrder 8.1.13. Table: Class 8.1.14. Table: ClassDetails 8.1.15. Table: Invoice 8.2. Insert Attributes, Validation Rules, Metadata, and Data types 8.3. Identify Primary and Foreign Keys 8.4. Create Relationships 8.5. Add limited testing data to all tables to test validation rules and integrity 8.6. Create Queries and Macros 8.6.1. Query: Employee Information for employee form 8.6.2. Query: Instructor Course and Class Qualification for form 8.6.3. Query: Course and Class information for form 8.6.4. Query: Member information for form 8.6.5. Query: Merchandise information and totals for invoice calculations 8.6.6. Query: Merchandise information for form 8.6.7. Query: Ordering and receiving information for vendor order form 8.6.8. Query: Vendor information and merchandise order totals 8.6.9. Query: Inventory information to show low inventory 8.6.10. Query: Member anniversary information for marketing purposes 8.6.11. Query: Generation of primary key numbers for forms to insert into tables 8.6.12. Query: Class list generation 8.6.13. Query: Active versus inactive members 8.6.14. Query: Membership type with count and gender parameters 8.6.15. Query: Customer invoice with transaction parameters 8.6.16. Query: Member average purchases 8.6.17. Query: Top merchandise sales count 8.6.18. Query: Update prices to order table after vendor order created 8.6.19. Query: Update prices to invoice table after customer purchase made 8.7. Create Forms for Data Entry 8.7.1. Form: Qualification 8.7.2. Form: Employee 8.7.3. Form: Position 8.7.4. Form: States 8.7.5. Form: Member 8.7.6. Form: FloridaCities 8.7.7. Form: Membership 8.7.8. Form: Course 8.7.9. Form: Merchandise 8.7.10. Form: Vendor 8.7.11. Form: VendorOrder 8.7.12. Form: Class 8.7.13. Form: ClassDetails 8.7.14. Form: Invoice 8.7.15. Form: Switchboard 8.8. Create Reports 8.8.1. Report: Qualified Instructors 8.8.2. Report: Employee 8.8.3. Report: Position 8.8.4. Report: Member 8.8.5. Report: Membership types, fees, and discounts

5|Page

Stephanie Chaney

ISDS 4113

November 27, 2013

9.

10.

11.

12.

13.

8.8.6. Report: Course 8.8.7. Report: Merchandise 8.8.8. Report: Vendor 8.8.9. Report: VendorOrder 8.8.10. Report: Class lists with class details 8.8.11. Report: ClassDetails, courses, and classes 8.8.12. Report: Invoice 8.8.13. Report: Member Anniversary 8.8.14. Report: Low Inventory Testing Phase 9.1. Insert data adequate for testing forms, tables, integrity, reports, and formulas 9.2. Team testing of database 9.3. Debug database 9.4. Install prototype version for testing onsite 9.5. Get feedback from users 9.6. Debug Delivery to Client 10.1. Install completed database at client location 10.2. Get feedback 10.3. Make any corrections as necessary and within scope unless additional time and funding provided 10.4. Create implementation and training strategy Training 11.1. Make training schedule 11.2. Train employees Documentation 12.1. Create database documentation for metadata 12.2. Create documentation for training Review 13.1. Review lessons learned 13.2. Complete anonymous team member evaluations 13.3. Document best practices for future use 13.4. Adjust MS Project template as necessary

6|Page

Stephanie Chaney
Risk Management Plan Risk Assessment Form Risk Event 1. One of the team members does not contribute their programming skills to the project due to personal and educational obligations Snow storm prevents programmers from having access to a computer to program The network storing the database goes down so client cannot test prototype and give feedback The database file closes down incorrectly and the file gets corrupted so programming is delayed or must be started over The client is slow giving the proper information regarding the business rules and processes necessary to design the database Likelihood

ISDS 4113

November 27, 2013

Impact

Detection Difficulty

When During planning, design, programming, and testing During the programming stage In the testing stage During programming stage Beginning of project during scope planning

5 1 3 3 4

5 3 3 5 3
Contingency Plan

3 2 1 1 3
Trigger Team member not turning in his or her programming assignments

2.

3.

4.

5.

Risk Response Matrix Risk Event 1. One of the team members does not contribute their programming skills to the project due to personal and educational obligations Snow storm prevents programmers from having access to a computer to program at a central location The network storing the database goes down so client cannot test prototype and give feedback The database file closes down incorrectly and the file gets corrupted so programming is delayed or must be started over The client is slow giving the proper information regarding the business rules and processes necessary to design the database Response Who Is Responsible

Avoid

2.

Mitigate

3.

Mitigate

4.

Mitigate

All other team members take on more load. Stephanie and the Lead Programmer discuss problem with the team member who is not contributing. At worst, the team member can be replaced if possible. Programmers take a copy of the daily backup and can work on the database from home. Any new data or programming can be imported and consolidated upon return. Install the prototype on each individual desktop computer at the clients facility instead of the network for testing and feedback. A backup of the database should be made daily so that the loss of the programming would at maximum only be the current days. Design of the database is based off the general knowledge and experience of health clubs and business procedures

Stephanie

Weather Report and conditions

Database Programmer

Arrival at clients facility and network is down Attempt to open the database file and find an error No information is forthcoming in the interview process

Stephanie

Lead Programmer

5.

Accept

Stephanie

7|Page

Vous aimerez peut-être aussi