71
Mission Science Information and Data Management System 3.0 Prototype Team3

Mission Science Information and Data Management System 3.0

  • Upload
    lynsey

  • View
    36

  • Download
    2

Embed Size (px)

DESCRIPTION

Mission Science Information and Data Management System 3.0. Prototype Team3. Team Operational Strengths/Weakness. Team Technical Strengths/Weakness. Open Win Conditions. - PowerPoint PPT Presentation

Citation preview

Page 1: Mission Science Information  and Data Management System 3.0

Mission Science Information and Data Management System 3.0

Prototype

Team3

Page 2: Mission Science Information  and Data Management System 3.0

Team 3/2

Team Operational Strengths/WeaknessStrengths Weaknesses Weakness MitigationAll team members are friendly and accommodating.

Latent response time to team emails.

Create and adhere to 24-hour response limitation to members the email is addressed to. Project manager to be responsible in reminding team members who do not reply promptly.

Quick and decisive in task delegation and responsibility.

Irregular meeting times and durations.

Hold a regular meeting time and place once a week.

High awareness in briefing teammates up to speed.

In-person meetings are seemingly a necessity (difficulty for DEN student).

Hold a regular meeting time and place once a week.

All team members value each other’s opinions.

Overall team does not have a high English proficiency.

DEN student to review all documentation prior to release/submission.

Page 3: Mission Science Information  and Data Management System 3.0

Team 3/3

Team Technical Strengths/WeaknessStrengths Weaknesses Weakness MitigationUnderstanding of database structures and query language.

Unfamiliarity with VBA Learning VBA in work.

Quick learners. Unclear understanding of the complete system.

Developer system trials and client interaction/communication to build system familiarity.

Have already achieved basic Search functionality.

System bugs/defects not fully understood.

Current system bugs/defects are being identified by the client/user.

Page 4: Mission Science Information  and Data Management System 3.0

Team 3/4

Open Win Conditions

■ Win Condition (WC_2712): As an administrator, I assign standardized names for tools, supplies and materials and consolidate multiple references to the same item.

■ Win Condition (WC_2594): As a student worker, I can view the inventory that have I reserved.

■ Win Condition (WC_2593): As a student worker, I can view the availability of material quantities and reserve them.

■ Win Condition (WC_2347): As an administrator, I can see available reserve and future needs of inventory.

■ Win Condition (WC_2346): As a student worker, I can input data so that I can save time(debug the existing problems identified on the proposal with data entry)

Page 5: Mission Science Information  and Data Management System 3.0

Team 3/5

OCD – System Purpose -- Yinlin Zhou

■ Allow instructors and student workers to design open-ended projects

■ Allow instructors to view the qualities of the programs and get feedbacks from kids.

■ Allow instructors and student workers to manage the inventories better.

Page 6: Mission Science Information  and Data Management System 3.0

Team 3/6

OCD – Program Model

Assumptions STEM projects are necessary for students to improve their learning skills The management of programs can decrease time cost The reported data is required as proof for funding The open-ended projects can help design the lesson more flexible The management of the inventory can improve inventory tracking

Stakeholders Initiatives Value Propositions Beneficiaries Developers Instructors USC Students Workers

Develop systems Create and design STEM

related projects Design open-ended lessons

For students to learn about STEM

Decrease amount of time managing programs

Easy report of data for funding

Improve kids critical thinking abilities

Increase retention in program

Increase flexibility to design lesson

Better inventories tracking

Instructors USC student workers Kids, elementary School

Students Funders

Cost Development costs Maintenance costs Data synchronized costs

Benefits Save time managing programs Increase availability of report data for funding Increase retention in program Increase flexibility in lesson design Save time managing inventories Improve kids critical thinking abilities

Page 7: Mission Science Information  and Data Management System 3.0

Team 3/7

OCD – Benefit Chain

Developers

Instructors

Develop systems

Create and design STEM

related projects

Design open-ended lessons

Increase kids interests in the

lessons and improve kids

learning abilities

Decrease amount of

time managing program

Easy report of data for

funding

Increase flexibility to

design lesson

Better inventories

tracking

Assumptions STEM projects are necessary for students to improve their learning abilities The management of programs can decrease time cost The reported data is required as proof for funding The open-ended projects can help design the lesson more flexibly The management of the inventory can improve inventory tracking

Improve kids critical

thinking

Increase retention in

program

Design main ideas of the

projects

Design details of the

lessons

Easier to check quantities of inventories

USC student workers

More different information and

ideas in the lessons

Get more resources

for the students

More interests in

the program

Help students learn by

themselves

Better managing program

Spend more time on lesson

design

Save time in program

management

Help collect feedback from

students

Save time in inventories

managementConsider more

details in lesson desgin

Page 8: Mission Science Information  and Data Management System 3.0

Team 3/8

OCD – System Boundary

Instructors and Darin

USC student workers

Microsoft AccessWindows 7

Create STEM projects Design STEM projects Design open-ended lessons Report data of the situations

of lessons Manage inventory

Page 9: Mission Science Information  and Data Management System 3.0

Team 3/9

OCD- Capability Goals

Capability Goals Priority LevelOC-1 STEM Project Management: Instructors should be able to create STEM projects for open-ended courses in database, and Student Workers should be able to create the relevant activities for the STEM projects.

Must have

OC-2 Survey Results Report System: Instructors should be able to view the results of surveys of students from the different activities.

Must have

OC-3 Inventory Management: Instructors and Student Workers should be able to view quantities of inventory, modify the situation of inventory and reserve the inventory

Must have

OC-4 Assign Next Generation Science Standards: Instructors should be able to assign Next Generation Science Standards for existing and new project activities.

Should have

OC-5 Check Completeness of student data: The system can automatically tell the instructors which fields are empty for every student.

Could have

Page 10: Mission Science Information  and Data Management System 3.0

Team 3/10

OCD- Level of Service Goals

Level of Service Goals

Priority Level

Referred WinWin Agreements

Availability Must have WC_2349, WC_2347Interoperability Must have WC_2593, WC_2348,

WC_2592

Page 11: Mission Science Information  and Data Management System 3.0

Team 3/11

OCD- Organizational Goals

■ OG-1: Improve elementary school students’ critical thinking

skills

■ OG-2: Increase retention in programs

■ OG-3: Help education organization easily report of data for

funding

■ OG-4: Increase elementary school students’ interests in science

■ OG-5: Help education organization get the feedbacks from

students

Page 12: Mission Science Information  and Data Management System 3.0

Team 3/12

OCD - Constraints

■ CO-1: Windows as an Operating System:

The new system must be able to run on Windows 7.

■ CO-2: Use MS Access 2010 as the tool:

The new system should be implemented on MS Access.

Page 13: Mission Science Information  and Data Management System 3.0

Team 3/13

OCD – Proposed New System

Element Relationship Diagram

Instructors

Student Workers

Survey Results Report

GeneratorDatabaseSurvey Creator

Modules Management

Activities Management

STEM Projects Management

Inventories Reserver

Inventories Management

Check Quantities of Inventories

STEM Projects

Main Ideas, Modules

Information

Details of Activities

Input Survey Information

Survey Results Collector

Results of Suveys

MSIDS 3.0

Page 14: Mission Science Information  and Data Management System 3.0

Team 3/14

OCD – Proposed New System

Business WorkflowBusiness Workflow

Student WorkerStudent Adminstrator

Check Inventory

Update Inventory

Receive Student Sign-

in Sheet

Update Sign-in Database

Fill in Sign-in Sheet

Generate Inventory

Report

Create Lessons and

Projects

Input into Lesson

Database

Perform Queries and

Generate Final Report

Do Pre&Post Survey

Design Pre&Post

Survey

Collect Pre&Post

Survey

Page 15: Mission Science Information  and Data Management System 3.0

Team 3/15

Win-Win Agreements

OCD Requirements

OC-1 Win Condition (WC_2595):As a student worker, I can create surveys for each activity completed from STEM projects

OC-5 Win Condition (WC_2592):As a student worker, I can check the completeness of students data. This system shall automatically tell me which fields are empty for every student.

OC-4 Win Condition (WC_2436):As an administrator, I can select Next Generation Science standards for existing and new project activities.

OC-2 Win Condition (WC_2435):As an administrator, I can review results of the students survey and attendance data.

OC-2 Win Condition (WC_2349):As an administrator, I can generate reports about students survey and attendance data.

OC-1 Win Condition (WC_2348):As a student worker, I can create activities from the STEM projects created by Administrator.

OC-1 Win Condition (WC_2345):As an administrator, I can create STEM projects so that students can create activities.

Page 16: Mission Science Information  and Data Management System 3.0

Team 3/16

Top 2 High Risks to Prototype -- Yinlin Zhou

■ Data communication between STEM Management System and current system

■ Design a report subsystem to allow clients to search anything they want

Page 17: Mission Science Information  and Data Management System 3.0

Team 3/17

Prototype

STEM

ID

Idea Keywords

Name Module

ID Name

ActivityStudent Survey

ID

Quests

N...N (Rela_STM_M)

1...N (Rela_M_A)

N...N (Rela_A_STU) 1..1 (Rela_A_SUR)

STMID

Rela_STM_M Rela_M_A

MID MID AID AID

Rela_A_SUR

SURID AID

Rela_A_STU

STUID

Prev_Score

Post_Score

Name

Inventory

Other Tables

MSIDMS 2.0

STEM MS

Page 18: Mission Science Information  and Data Management System 3.0

Team 3/18

Report Subsystem GUI Design

Page 19: Mission Science Information  and Data Management System 3.0

Team 3/19

Report Subsystem Search Example

Page 20: Mission Science Information  and Data Management System 3.0

Team 3/20

Implement Dynamic List Box

Page 21: Mission Science Information  and Data Management System 3.0

Team 3/21

Prototype Test 1

Result of Search STEM By Module

Page 22: Mission Science Information  and Data Management System 3.0

Team 3/22

Prototype Test 2

Result of Search Student By Activity

Page 23: Mission Science Information  and Data Management System 3.0

Team 3/23

Prototype Test 3

Result of Search STEM By Student

Page 24: Mission Science Information  and Data Management System 3.0

Team 3/24

Architecture

■ System Context Diagram■ Behavior of the System■ Use Cases

Chenguang Liu

Page 25: Mission Science Information  and Data Management System 3.0

Team 3/25

System Context System

Page 26: Mission Science Information  and Data Management System 3.0

Team 3/26

Behavior of the System

Page 27: Mission Science Information  and Data Management System 3.0

Team 3/27

Use Cases

■ Create STEM Project

Page 28: Mission Science Information  and Data Management System 3.0

Team 3/28

Use Cases

■ Create STEM Project

Page 29: Mission Science Information  and Data Management System 3.0

Team 3/29

Use Cases

■ Create Activity

Page 30: Mission Science Information  and Data Management System 3.0

Team 3/30

Use Cases

■ Create Activity

Page 31: Mission Science Information  and Data Management System 3.0

Team 3/31

Use Cases

■ Create Survey

Page 32: Mission Science Information  and Data Management System 3.0

Team 3/32

Use Cases

■ Create Survey

Page 33: Mission Science Information  and Data Management System 3.0

Team 3/33

Use Cases

■ Search

Page 34: Mission Science Information  and Data Management System 3.0

Team 3/34

Use Cases

■ Search

Page 35: Mission Science Information  and Data Management System 3.0

Team 3/35

Life Cycle Plan

■ Strategy■ Increments■ Responsibility■ Recourses

Fei YU

Page 36: Mission Science Information  and Data Management System 3.0

Team 3/36

Life Cycle Plan

■ Life Cycle Strategy: ICSM

■ Increments in Development phase and transition: Construction iteration Core Capability Drivethrough Transition Readiness Review

Page 37: Mission Science Information  and Data Management System 3.0

Team 3/37

Current Status

■ As a one semester team, we are currently still in the foundation phase.

■ Both items in foundation phase and development phase will be planned

Page 38: Mission Science Information  and Data Management System 3.0

Team 3/38

Key Stakeholder Responsibility

Fei YUProject Manager, Life cycle plannerTeam Management, Plan for life cycle

Yunpeng CHENRequirement Engineer, Feasibility EngineerInteract with clients. Identify requirementsp Feasibility evidence

Yinlin ZHOUPrototyper, Operational Concept EngineerPrototypeDevelop operational concept

Amy PENGTester, Builder, UML modelerDevelop the systemTest the system

DarinClientGive feedback for the development.

Steven LeeQFP, Requirement EngineerIdentify requirements, Monitor quality during development

Katherine LIUSoftware ArchitectureDevelop Software ArchitectureDevelop Develop system.

Page 39: Mission Science Information  and Data Management System 3.0

Team 3/39

Project Plan

Page 40: Mission Science Information  and Data Management System 3.0

Team 3/40

COINCOMO II

Page 41: Mission Science Information  and Data Management System 3.0

Team 3/41

Feasibility Evidence

■ Process Feasibility■ Personnel Costs■ Quantitative Benefits■ ROI■ Major Risks■ Level of Service Feasibility■ Capability Feasibility

Yunpeng Chen

Page 42: Mission Science Information  and Data Management System 3.0

Team 3/42

NDI/NCS Evaluation & Analysis Process Feasibility

Criteria Importance

Project Status

Rationales

30 % of NDI/NCS features

3 4 The project will use the system of Microsoft Access as a NDI.

Single NDI/NCS 3 4 The project will use only Microsoft Access as a NDI.

Unique/ inflexible business process

1 1 The business process is very flexible.

Need control over upgrade / maintenance

3 2 This project needs to be upgraded and maintained in the future.

Rapid deployment 1 1 The program does not need to be deployed rapidly to market

Critical on compatibility

3 2 The new system needs to be compatible with the old one

Internet connection independence

1 1 The system can be standalone system on local computers

Need high level of services / performance

1 1 The system does not need to perform in

Need high security 2 2 The system will be used by only by administrator and student workers.

Asynchronous communication

1 1 The system does not need to communicate with others.

Be accessed from anywhere

2 2 The database will be used from several end by different student workers.

Critical on mass schedule constraints

3 3 The system will effect on several people schedule.

Lack of personnel capability

1 2 The system does not rely on individual.

Require little upfront costs

3 3 The project does not have any budget.

Require low total cost of ownership

3 3 The project does not have any budget.

Not-so-powerful local machines

3 3 The system can be run on a regular machine.

Page 43: Mission Science Information  and Data Management System 3.0

Team 3/43

Business Case Analysis----Personnel Costs

Activities Time Spent (Hours)Development Period  

Valuation and Foundation Phases: Time Invested (CS577a, 4 weeks)

 

Client: Meeting via email, phone, in-person and other channels [3 hrs/week * 4 weeks * 2 people]

24

Group: Meeting via email, gtalk, in-person and other channels [4 hrs/week * 4 weeks * 6 people]

96

Architecture Review Boards [3 hrs * 2 times * 6 people] 36Development and Operation Phases: Time Invested (CS577a, 5 weeks)

 

Client: Meeting via email, phone, in-person and other channels [3 hrs/week * 5 weeks * 2people]

30

Maintainer: Meeting via email, phone, and other channels [4 hrs/week * 5 weeks * 2 people]

40

Architecture Review Boards and Core Capability Drive-through session [3 hrs * 4 times * 6 people]

72

Group: Meeting via email, gtail, in-person and other channels [4 hrs/week * 5 weeks * 6 people]

120

Development of system in operation phase and training Installation and deployment [1 hrs * 1 times * 2 people] Training and Support [1 hrs * 2 times * 2 people]

6

Total 424Maintenance Period (3 years)  Maintenance (0.5 hrs/week * 156 weeks * 1 people) 78Total  

Page 44: Mission Science Information  and Data Management System 3.0

Team 3/44

Business Case Analysis----Quantitative Benefits

Current activities & resources used % Reduce

Time Saved (Hours/Year)

Checking the inventory (50times * 30 mins) 40 10Create survey to STEM activity (100 times * 30 mins) 50 25

Extract the survey reports as Excel files(50times * 60 mins) 90 45

Create STEM project (20 times * 30 mins) 50 5Create lesson plans for STEM project (100 times * 30 mins) 50 25

Track material in the inventory for STEM project (30times * 60 mins) 50 15

Obtain searching results ( 100 times * 30mins) 60 30Manage student information(30 times * 60 mins) 50 15

Total 170

Page 45: Mission Science Information  and Data Management System 3.0

Team 3/45

Business Case Analysis----ROI

Year CostBenefit(Effort Saved)

Cumulative Cost

Cumulative

BenefitROI

2013 424 0 424 0 -12014 26 170 450 170 -0.62015 26 170 476 340 -0.32016 26 170 502 510 0.01

CE/通用格

式CE/通用格

式CE/通用格

式CE/通用格

CE/通用格式

CE/通用格式

CE/通用格式ROI

Page 46: Mission Science Information  and Data Management System 3.0

Team 3/46

Major Risks

Risks

Risk Exposure

Risk MitigationsPotential Magnitude

Probability Loss

Risk Exposure

Incorporate STEM subsystem into the existing system

8 9 72 Develop the STEM subsystem and use activity as the link between existing system and STEM subsystem

Multiple searching methods to get student data and output it

8 7 56 Use two listboxes and the input keyword to implement the searching methods

Add Reporting subsystem to the existing system

6 7 42 Create survey database table and interface and interact with activity and student worker.

Fix current bugs in the system 6 3 18 Get user feedback from the client on urgent fixes.

Upgrade GUI to be more user-friendly

5 3 15 Continually communicate with client for recommendations and feedback.

Page 47: Mission Science Information  and Data Management System 3.0

Team 3/47

Level of Service Feasibility

■ Interoperability: System must be available for every student worker to manipulate on the entire system and do his own operations. According to the win-win agreements of : WC-2593 WC-2348 WC-2592

■ Availability: System must be available at least 12 hours a day. According to the win-win agreements of : WC-2349 WC-2347

Page 48: Mission Science Information  and Data Management System 3.0

Team 3/48

Capability Feasibility

Capability Requirement Product SatisfactionCR-1 : Create STEM Project Software/Technology used: Microsoft Access

Feasibility Evidence: Microsoft Access is capable of matching STEM project interface and STEM project table together. And advisor can add STEM project data to database and system will automatically verify if an identical STEM project exists, if not, data added successfully.

Referred use case diagram: UC 1CR-2 : Create Activity Software/Technology used: Microsoft Access

Feasibility Evidence: Microsoft Access is capable of linking activity interface and Activity table together. And student workers can add activities to the existing STEM projects it belongs to.

Referred use case diagram: UC 3CR-3 : Create Survey Software/Technology used: Microsoft Access

Feasibility Evidence: Microsoft Access is capable of.matching survey interface and survey table together. And student workers can add to database, with owner relationship with STEM activity.

Referred use case diagram: UC 2CR-4 : Searching Methods and Extract result as Excel files

Software/Technology used: Microsoft AccessFeasibility Evidence: Microsoft Access supports different searching queries to the database table and show result in the interface.. Then, if the client wants to extract the report, they can save as Excel filesReferred use case diagram: UC 4, UC 5

Page 49: Mission Science Information  and Data Management System 3.0

Team 3/49

Basic Demographic: Science Coordinator, Pre-College Programs, Viterbi School of Engineering, USC

Attributes- Experienced in teaching and

education management- Specialist of kids’ development

Description Darin is the administrator of Mission Science Program. He coordinates the activities and manage the program budget for nine elementary and middle school-based science clubs, develop standards-based curriculum for "hands on" projects, activities and experiments.

User ScenarioRecently, a new national standard project-STEM has come into use. Darin needs to incorporate the new project into the system. Current system does not support the new kind of project’s organization, which is that projects include several modules, and modules are consist of several activities. Student worker can create their own activities based on the overarching idea of the project that Darin comes up with.

Goals & Aspirations- Incorporate STEM into current

system- Improve current system

functionality

Darin Gray

Page 50: Mission Science Information  and Data Management System 3.0

Team 3/50

Stephanie

Basic Demographic: Age: 19Undergraduate Student

DescriptionStephanie is a Science Educator that enjoys working with students in the middle school and elementary school grade levels. She is a recent undergraduate who is interested in teaching and developing middle school science curriculum. She has spent many hours volunteering and working with students in elementary and middle school classrooms.User ScenarioStephanie is responsible for analyzing and quantify students’ answers to numerous surveys regarding the science heuristic model. She has to collect all the surveys of one activity and analyze if students learn from the activity. She is exhausted dealing with all the results of survey manually.

Attributes- Passionate about helping

kids- Good at collecting

information

Goals & Aspirations- Survey management system- Reduce manual work- Extract survey searching

result files

Page 51: Mission Science Information  and Data Management System 3.0

Team 3/51

Basic Demographic: Age: 22Graduate Student in Children Development

Attributes- Passionate- Willing to help kids

Description Larren, an information specialist, is comfortable guiding students to the resources they need.Lauren’s long-term goal is to become a counselor in the office, and she enjoys collaborating with the counselors and advisers. Learning about all the forms and verifications that international students need has been challenging, but Lauren learns something new every day.

User ScenarioLauren needs to create activities based on the overarching idea of a project. Currently, she needs to write create activity report with hand and hand in to her supervisor to verify. She wants a create activity entry for her to input all the activity information into the database.

Goals & Aspirations- Create Activity Entry- Create Student Information

Entry- Create lesson plans

Lauren Brown

Page 52: Mission Science Information  and Data Management System 3.0

Team 3/52

Basic Demographic: Age: 23Graduate Student

Attributes- Passionate- Willing to help kids

Description Badashian, an information specialist, is comfortable guiding students to the resources they need.“I really want to be able to answer the questions students have instead of referring them to counselors for every little question they ask,” she said. “I’m really excited to get my foot in the door and start helping as much as I can.”

User ScenarioBadashian’s long-term goal is to become a counselor in the office, and she enjoys collaborating with the counselors and advisers. Learning about all the forms and verifications that international students need has been challenging, but Badashian learns something new every day.

Information Sources- Facebook- 5 minutes for mom website- Local paper- Grey’s anatomy

Natalie Badashian

Goals & Aspirations- Create Activity Entry- Create Student Information

Entry- Create lesson plans- Manage Inventory

Page 53: Mission Science Information  and Data Management System 3.0

Team 3/53

Larry Lim

Basic Demographic: Age: 23Graduate Student

Attributes- Passionate- Willing to help kids

Description Lim, an information specialist, is comfortable guiding students to the resources they need.“I really want to be able to answer the questions students have instead of referring them to counselors for every little question they ask,” she said. “I’m really excited to get my foot in the door and start helping as much as I can.”

User ScenarioLim’s long-term goal is to become a counselor in the office, and she enjoys collaborating with the counselors and advisers. Learning about all the forms and verifications that international students need has been challenging, but Badashian learns something new every day.

Information Sources- Facebook- 5 minutes for mom website- Local paper- Grey’s anatomy

Goals & Aspirations- Track the items for activities

in the Inventory- Manage Inventory

Larry Lim

Page 54: Mission Science Information  and Data Management System 3.0

Team 3/54

Quality Focal Point

■ Traceability Matrix■ Defect Identification■ Current Defect Matrix■ Quality Management Strategy

Steven LEE

Page 55: Mission Science Information  and Data Management System 3.0

Team 3/55

Traceability Matrix (Part 1)

OCD Requirements Use Case Test Case

OC-1 Win Condition (WC_2595):As a student worker, I can create surveys for each lesson completed from STEM modules

UC-2 CreateSurvey01

OC-5 Win Condition (WC_2592):As a student worker, I can check the completeness of students data. This system shall automatically tell me which fields are empty for every student.

N/A N/A

OC-4 Win Condition (WC_2436):As an administrator, I can select Next Generation Science standards for existing and new project activities.

UC-3 N/A

OCD Description1 STEM Project Management2 Survey Results Report System3 Inventory Management4 Assign Next Generation Science

Standards5 Check Completeness of Student Data

Use Case

Description

1 Create STEM Project2 Create Survey3 Create Activity4 Search

Page 56: Mission Science Information  and Data Management System 3.0

Team 3/56

Traceability Matrix (Part 2)

OCD Requirements Use Case Test Case

OC-2 Win Condition (WC_2435):As an administrator, I can review results of the students survey and attendance data.

UC-4 ViewReport01ViewReport02ViewReport03

OC-2 Win Condition (WC_2349):As an administrator, I can generate reports about students survey and attendance data.

UC-4 CreateSurvey01

OC-1 Win Condition (WC_2348):As a student worker, I can create lessons from the STEM modules created by Administrator.

UC-1 CreateActivity01CreateActivity02

OC-1 Win Condition (WC_2345):As an administrator, I can create STEM modules so that students can create activities.

UC-1UC-3

CreateSTEM01CreateSTEM02CreateSTEM03

OCD Description1 STEM Project Management2 Survey Results Report System3 Inventory Management4 Assign Next Generation Science

Standards5 Check Completeness of Student Data

Use Case

Description

1 Create STEM Project2 Create Survey3 Create Activity4 Search

Page 57: Mission Science Information  and Data Management System 3.0

Team 3/57

Defect Identification

Document Section/UML/Code Review Strategy / Defect DetectionFED, OCD, LCP, PRO, SID, SSAD Peer Review, ARB, BugzillaMSIDMS VBA Peer Review, Prototyping, Client/User

Feedback, BugzillaRequirements Change Win-Win negotiation, Incremental

Function DevelopmentUML Team Review Board, Client/User

Engagement, Bugzilla

Page 58: Mission Science Information  and Data Management System 3.0

Team 3/58

Current Defect Matrix (Bugzilla)

System Defect / Bug Description MitigationInventory from Darin's description

The total size limit for Microsoft Access could not go over to 2GB, which forces separate storage of current data

In work. Low Priority.

Inventory Management Duplicate inventory storage in different database

In work. Low Priority.

Student Name duplicate detection function instability

Sometime this function (finding if two student in the database is the same) is working and sometimes not.

In work. Low Priority.

Phase Exploration

Valuation

Bugs/Defects Detected

3 0

Page 59: Mission Science Information  and Data Management System 3.0

Team 3/59

Current Defect Matrix (Bugzilla)

Page 60: Mission Science Information  and Data Management System 3.0

Team 3/60

Quality Management Strategy

Document Type Quality-/Config-Mgmt Strategy Room for Improvement

MSIDMS VBA Version Control:•ReadMe file that is updated after each version release of the Database Master Copy.•Standard commenting method to annotate updates/modification.

In work.

MSIDMS VBA Bugzilla None identified.Documents DropBox None identified.

Page 61: Mission Science Information  and Data Management System 3.0

Team 3/61

Quality Management StrategyVersion Control Example

Page 62: Mission Science Information  and Data Management System 3.0

Team 3/62

Acceptance Test Plan and Cases

■ Acceptance Criteria■ Test Cases■ Test Case Demo

Jingwen Peng

Page 63: Mission Science Information  and Data Management System 3.0

Team 3/63

Acceptance Criteria

Page 64: Mission Science Information  and Data Management System 3.0

Team 3/64

Test Cases

Page 65: Mission Science Information  and Data Management System 3.0

Team 3/65

Test Case Demo

Page 66: Mission Science Information  and Data Management System 3.0

Team 3/66

Test Case Demo

Page 67: Mission Science Information  and Data Management System 3.0

Team 3/67

Test Case Demo

Page 68: Mission Science Information  and Data Management System 3.0

Team 3/68

Test Case Demo

Page 69: Mission Science Information  and Data Management System 3.0

Team 3/69

Test Case Demo

Page 70: Mission Science Information  and Data Management System 3.0

Team 3/70

Test Case Demo

Page 71: Mission Science Information  and Data Management System 3.0

Team 3/71

Questions