Game-based Learning System Software Development Plan (SDP) Ver. < 1.1 >

Transcription

1 Game-based Learning System Software Development Plan (SDP) Ver. < 1.1 > Group 2 Systemdevelopment and documentation 1

2 Table of Contents Table of Contents Preface Introduction Purpose Scope Project Overview Project Purpose, Scope and Objective Assumptions and constraints Deliverables Project Organization Software Process Model Description Hardware and Software Resource Requirements Work schedule Monitoring and Reporting Mechanisms Tools... 8 Group 2 Systemdevelopment and documentation 2

3 Project Organization & Project Overview Preface This document was created to describe the development process for the software DOON that we ve made for the customers Olav Dæhli and Hans Petter Halvorsen. Table 1: Shows document version history. Version number Commentary Changes made 1.0 Draft of System document Titles added. with titles and text in correct Texts added. format. Figures and tables created. 1.1 Added Preface Spellchecked every Chapter. Removed and updated crossreferences. Inserted Captions. Added Staff and Version history in preface. Table 2: Shows current staff and contact information. Name Cell# Role Nilsen, Casper Systems Engineer Heldal, Sander Systems Engineer Torsdal, Martin Systems Engineer Larsen, Kenneth Systems Engineer Group 2 Systemdevelopment and documentation 3

4 Project Organization & Project Overview 1. Introduction 1.1. Purpose The purpose of this Software Development Plan is to describe the methods used in developing DOON Scope This Software Development Plan is developed in association with a student group project for our Application. It is designed in cooperation with the University College of Southeast Norway. 2. Project Overview 2.1. Project Purpose, Scope and Objective The purpose of this project is to make a Game-based Learning System in the form of a quiz game. Our group has been given the job to meet the expectations of our clients to this system. The objective is to make an easy-to-use, efficient, secure and informative quiz game. The system is expected to be an online multiplayer quiz game for educational purposes Assumptions and constraints The project is projected to last for 127 days according to Figure 1: Gantt Chart. The members of this project are estimated to have a workload of 270 hours each during this period. These 270 hours are calculated from the 15 hours the clients expect every member to work every week times the 18 or so weeks the project will be under development. Of the 15 expected hours every week there is 4 fixed working hours every Tuesday and Friday from 10:15 AM to 14:00 PM UTC+01:00. The remaining 7 hours of work is the expected amount of labor outside of working hours. With the all-together 1080 working hours the team can t guarantee that the goals for each week will be met on time. This is on account of the uncertain amount of hours required to complete each particular goal. However, the team aspires to fulfill the target goals regardless of this uncertainty. The student budget for this project is assumed and hoped to stay at zero Deliverables The team expects to deliver the following documents: Software Development Plan, UML diagrams, CAD drawings, System Documentation, ER Diagram, SRD Document, User Manuals and Finished System. Group 2 Systemdevelopment and documentation 4

5 Project Organization 3. Project Organization The development team consists of four students from the University College of Southeast Norway. Casper Nilsen, Kenneth Larsen, Martin Torsdal and Sander Heldal. All four members are system engineers who each will have multiple roles as programmer, Software Tester, UX Designer and Software Architect. 4. Software Process Model Description We will be using the Scrum method of product development which is an Agile Software Development framework. Scrum requires the owners to create a product backlog which is a wish-list with different priority levels for the finished product. Under the implementation phase it will be conducted sprint sessions, which means chunks of the product backlog will be sorted to smaller sprint backlogs which we implement them into the system. Since we aren t able to perform daily Scrums we will assess progress at working hours. It is necessary that the Scrum Values are upheld throughout the project. The values are commitment to achieve our goals. The courage to work through challenges. To focus on the goal and Sprint Backlogs. To be transparent about work and challenges and to respect each other s capabilities. Group 2 Systemdevelopment and documentation 5

6 Hardware and Software Resource Requirements 5. Hardware and Software Resource Requirements Hardware: Personal Computer. Software: Microsoft Project Professional Visual Studio Enterprise SQL Server Microsoft Visio VSTS Visual Studio Team Services. Microsoft OneDrive. Facebook Messenger. CA ERwin Data Modeler r9.6. Group 2 Systemdevelopment and documentation 6

7 Work Schedule 6. Work schedule Figure 1: Gantt Chart shows expected work schedule in detail. Figure 1: Gantt Chart Group 2 Systemdevelopment and documentation 7

8 Monitoring and Reporting Mechanisms & Tools 7. Monitoring and Reporting Mechanisms We will be utilizing software specified in Hardware and Software Resource Requirements to communicate. Progress will mainly be shared through VSTS (Visual Studios Team Services) and as often as necessary and semi-weekly meetings with the customer. There will also be revision of progress every week at working hours which is specified under Assumptions and constraints. The group will share information through VSTS, , Facebook Messenger and under working hours. 8. Tools Book: I, Sommerville, Software Engineering: Pearson, 2015 Website: Group 2 Systemdevelopment and documentation 8