use case, waterfall, data dictionary and context diagrams

3800Portfolio.docx

Home >Information Systems homework help >use case, waterfall, data dictionary and context diagrams

INFS 3800

Portfolio (15 points)

A small fitness studio wants a mobile app developed. The studio is class based only and operates 7 days a week. The class types are indoor cycling, barre, and bounce. The schedule is different depending on the day. There are multiple instructors and staff. Equipment is provided but, in some cases, can be rented. There is a small on site shop that is online as well. The app needs to incorporate the following. The list is just a start but could be expanded or reduced.

Class signup

Payments

Online shop purchases

Reporting

Scheduling Classes

Instructor assignments

Communication

1. Fitness Studio – General

a. Stakeholder analysis

· Create stakeholder matrix to analyze stakeholders.

· Must include minimum of 5 stakeholder groups.

· Correct format must be used to receive full credit.

· (see example)

b. Data dictionary

· Must include minimum of 25 entries.

· Must include minimum of ID, Business Data Object, Field Name, Description, Unique Values?, Data Type, Length, and Valid Values.

· Correct format must be used to receive full credit.

· (see example)

2. Fitness Studio - Waterfall

a. Context diagram

· Correct format must be used to receive full credit.

· (see example)

b. Requirements

· Must include a minimum of 15 requirements.

c. MoSCoW

· Prioritize all requirements from 2.b using MoSCoW.

· Must include all the requirements from 2.b.

· (Separate section from 2.b)

d. Use case

· Create 3 complete use cases.

· Correct format must be used to receive full credit.

· (see example)

3. Fitness Studio - Agile

a. User stories

· Must include a minimum of 15 user stories.

· Correct format must be used to receive full credit.

· Example: “As an <actor>, I want to be able to <function>, so that I can <business reason>”

b. Use case diagram

· Create 2 use case diagrams.

· Correct format must be used to receive full credit.

· (see example)

c. First three sprints

· Create the first three sprints from the user stories.

· Must include user stories from 3.a.

· First sprint must be MVP.

d. Wireframe for one screen

· Must include a screen title.

· Correct format must be used to receive full credit.

· (see example)

Diagram and Model Examples to Use

1.a. Stakeholder Analysis (Stakeholder Matrix)

PMI Guide to BA - Section 5.2.2.4 (pages 119-120) *example

BA for Practitioners - Section 3.4 (pages 39-45)

1.b. Data Dictionary

PMI Guide to BA – Figure 7-7, Section 7.2.2.2 (Pg. 187-188)

BA for Practitioners – Figure 4-13, Section 4.10.10.3 (Pg. 108-110) *example

2.a. Context Diagram

PMI Guide to BA – Figure 7-6, Section 7.2.2.1 (Pg. 186-187) *example 1

BA for Practitioners – Figure 4.4, Section 4.10.7.3 (Pg. 95-96) *example 2

2.d. Use Case

PMI Guide to BA – Figure 7-32, Section 7.3.2.8 (Pg. 214-215) *example

BA for Practitioners – Table 4-4, Section 4.10.8.2 (Pg. 100-102)

3.b. Use Case Diagram

PMI Guide to BA – Figure 7-27, Section 7.2.2.18 (Pg. 206) *example 1

BA for Practitioners – Figure 4-6, Section 4.10.7.5 (Pg. 97-98) *example 2

3.d. Wireframe

PMI Guide to BA – Figure 7-20, Section 7.2.2.13 (Pg. 199-201) *example

BA for Practitioners – Figure 4-20, Section 4.10.11.4 (Pg. 115-117)