Part A - Project Management (25%)
Submission Requirements
This assignment must be submitted online. Your submission should include:
· Project Plan.docx - A project plan document. You should use the provided template.
· Software Design Document.docx - A software design document. You should use the provided template.
· Gantt chart.xlsx - A separate Gantt chart (high-resolution version). You should embed this in your project plan (as an image or other), but also provide the original file.
· git_log.txt - A copy of the Git Log
· Any other documents/supporting files you have created that you think are necessary to include at this stage
In Part A, you will need to prepare a project plan that includes a Project Overview, Work-Breakdown Structure, Activity Definition and estimation and a Gantt chart for displaying scheduling & time estimation. This project plan should include sensible estimates for the various tasks required for both Part A and B (including estimates on preparing the project planning documentation). As you complete various components, you should put the actual completion time/dates on your Gantt chart to track how close you were to your estimates. For the subsequent stage of the assignment, you should revise your project plan with any additional details and continue to track your work.
You will then need to prepare a Software Design Document for one of the given data sets and related questions. You should start with a System Vision Statement (this can be included in your design document). You should then produce a formal list of requirements that need to be satisfied, some use cases for your software, a listing of system components and the related software design, and an early user interface design/wireframe (to be implemented in part B). There are templates provided for these documents. Please read the template documents for more hints and guidance.
Datasets
There is a dataset available for you to do your assignment on. Each dataset has a set of required analysis functions. Remember, in addition to the listed required analysis tools, you must come up with 1 additional analysis task/tool of your own.
Victoria State Accident DataSet
https:
www.kaggle.com/gaurav896/victoria-state-accident-dataset
Required Features:
· For a user-selected period, display the information of all accidents that happened in the period.
· For a user-selected period, produce a chart to show the number of accidents in each hour of the day (on average).
· For a user-selected period, retrieve all accidents caused by an accident type that contains a keyword (user entered), e.g. collision, pedestrian.
· Allow the user to analyze the impact of alcohol in accidents – ie: trends over time, accident types involving alcohol, etc.
· One other ‘insight’ or analysis tool of your choice
Project Plan
Project Name
Student Names
Table of Contents
1.0 Introduction 3
1.1 Problem Background 3
1.2 Scope 3
1.3 Document contents 3
2.0 Work Breakdown Structure 4
3.0 Activity Definition & Estimation 5
4.0 Gantt Chart 6
1.0 Introduction
1.1 Background
1.2 Scope
1.3 Document contents
Include some background information about the problem, the scope and what this document will contain.
2.0 Work Breakdown Structure
This section should include the work
eakdown structure for the whole project. The elements from the WBS should be used to generate your activity definition and those activities should then be scheduled in the Gantt Chart. Remember to consider ALL project activities – anything you do or will need to do should be included in the WBS
WBS’s are usually presented as some kind of hierarchical diagram/chart etc. The details what is involved each work unit should be provided in section 3: Activity Definition
You do NOT need to do a WBS Dictionary for this project – the activity definition (whilst slightly different) will suffice. The WBS is focussed on SCOPE. The Activity definition is focussed on TIME.
3.0 Activity Definition & Estimation
From your WBS, define the activities required for your project. You will revise this document and add more detail for part B as you discover more about the project.
Each activity should be clearly identified by a number and should match up to your Gantt chart. You should provide some estimations for the time you think each activity will take. This should make it easy to prepare your Gantt chart.
4.0 Gantt Chart
This section should contain your Gantt chart. The items in the Gantt chart should match the activity definition from section 3. You should also submit your Gantt chart file separately.
Software Design Document
Project A- Testing
Student Names
Table of Contents
1.0 System Vision 3
1.1 Problem Background 3
1.2 System Overview 3
1.3 Potential Benefits 3
2.0 Requirements 4
2.1 User Requirements 4
2.2 Software Requirements 4
2.3 Use Cases 4
3.0 System Components and Software Design 5
3.1 System Components 5
3.2 Software Design 5
4.0 User Interface Design 6
1.0 System Vision
1.1 Problem Background
1.2 System Overview
1.3 Potential Benefits
2.0 Requirements
2.1 User Requirements
In this section you detail how a user is supposed to interact with or use your program. What do they need to be able to do? This should all be from the end users perspective. Can be a combination of na
ative text and listing of needs.
Assignment note: You have not been given a client/user, so you can make one up. Who do you think would be using your software?
2.2 Software Requirements
In this section you detail what the requirements for the software are. What functionality will it provide? This is usually a formal listing, with requirements often using the word ‘Shall’. IE:
R1.1 The program shall accept multiple file names as arguments from the command line.
R1.2 Each file name can be a simple file name or include the full path of the file with one or more levels.
etc …
Can be primarily functional requirements, though you may include other types if you think of them.
2.3 Use Cases & Use Case Diagrams
In this section you provide some use cases showing how people may use your software.
3.0 Software Design and System Components
3.1 Software Design
A block diagram/flowchart of how your software might work
3.2 System Components
3.2.1 Functions
Preliminary list of all functions in the software. For each function in the list the following information is provided:
· a
ief description of what it does (1 or 2 sentences);
· a list of the input parameters, and their data types, and what they are used for;
· a list of any side effects caused by the function (ie change global or member variables, changes data passed by reference from calling function etc)
· a description of the function’s return value
3.2.2 Data Structures / Data Sources
List of all data structures in the software (eg linked lists, trees, a
ays etc) or eternal data sources. For each data structure in the list the following information is provided:
· Type of structure (tree, list etc),
· Description of where and how it is used
· List of data members, and what each one is for do
· List of functions that use it
3.2.3 Detailed Design
Pseudocode for all non-standard / non-trivial algorithms that operate on data structures
4.0 User Interface Design
This is your initial interface design. Describe the tools you used for this design stage and any key findings that informed your design. This introduction is descriptive and should explain what you have completed for the actual design work you will present in the sub-sections below.
4.1 Structural Design
Structural design refers to the navigational and information structure of your product – the structure that supports the interface layout. How will you structure your product? How will you group your information? How will you navigate through your product? Why? This can take the form of a diagram showing structure and hierarchy, supported by a discussion and justification of your choices. Why have you made these design choices? Describe and outline the structure of your interface and of your information.
4.2 Visual Design
Detail your visual design: Layout, visual elements, icons, graphics, style, colour, fonts general screen designs. This can be sketches, wireframes, mockups etc, supported by a discussion, explanation, and justification of your choices.
Project Planne
Project Title
Select a period to highlight at right. A legend describing the charting follows. Period Highlight: 1 Plan Duration Actual Start % Complete Actual (beyond plan) % Complete (beyond plan)
ACTIVITY PLAN START PLAN DURATION ACTUAL START ACTUAL DURATION PERCENT COMPLETE PERIODS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Activity 01 1 5 0%
Activity 02 0%
Activity 03 0%
Activity 04 0%
Activity 05 0%
Activity 06 0%
Activity 07 0%
Activity 08 0%
Activity 09 0%
Activity 10 0%
Activity 11 0%
Activity 12 0%
Activity 13 0%
Activity 14 0%
Activity 15 0%
Activity 16 0%
Activity 17 0%
Activity 18 0%
Activity 19 0%
Activity 20 0%
Activity 21 0%
Activity 22 0%
Activity 23 0%
Activity 24 0%
Activity 25 0%
Activity 26 0%
Activity 27 0%
Activity 28 0%
Activity 29 0%
Activity 30 0%
Activity 31 0%
Activity 32 0%
Activity 33 0%
Activity 34 0%
Activity 35 0%