DOC

Project introduction

By Sandra Hicks,2014-04-14 00:59
12 views 0
The Design stage has 2 major milestones: Complete High-level design specification Complete deliverable high level design specification

Project introduction

    Project outline

    This document outlines the project plan for Software House 2’s, Software engineering project.

    The aim of this project is to design a renderer for simple HTML files. The renderer itself will be able to read and translate a HTML file into a format appropriate for a screen. The system should be built in agreement with the initial customer requirements - as well as any additional requirements discussed and agreed upon at the customer meeting.

    We will go about tackling the project by dividing our software house into smaller groups of 2-3 members. Each section team will have particular responsibilities with regard to; analysis, design, implementation and quality assurance in order to see the project is completed successfully and within the time-limits set.

    This project will be carried out according to the guidelines of the Software Engineering quality manual.

    Project schedule

    The project has four main milestones.

    By 4pm Monday of Week 7, the following documents should be delivered to the customer:

    ? The Project Plan. By 4pm Monday of Week 10, the following documents should be delivered to the customer:

    ? The Requirements specification,

    ? The Acceptance criteria, and

    ? The High-level design specification. By 4pm Monday of Week 3, the following documents should be delivered to the customer:

    ? The Detailed design specification. By 4pm Thursday of Week 8, the following documents should be delivered to the customer:

    ? The Source code,

    ? The Test specification,

    ? The User documentation.

Phase plan

    Project phases

    Planning

    Tasks:

    ? Organise software house in section teams

    ? Establish overall project outline

    ? Establish major milestones

    Responsibility: These 3 tasks will be the responsibility of the entire team as a whole

    ? Identify roles within section teams

    ? Identify phases within sections

    ? Identify tasks within phases

    Responsibility: These 3 tasks will be the responsibility of each section team

Requirements analysis

    Milestones:

    The Requirements Analysis Phase has 7 major milestones:

    1. Establish requirements with customer

    2. Complete scenario based analysis by Thurs, week 5

    3. Complete acceptance criteria by Wednesday, week 6

    4. Complete class based analysis by Wednesday, week 6

    5. Complete behaviour based analysis, by Wednesday, week 6

    6. Complete flow based analysis, by Wednesday, week 7

    7. Compile deliverable ‘requirements specification’ by Thursday, week 7

Tasks:

    ? Establish requirements with customer

    o Discuss requirements with customer at customer meeting Responsibility: This will be carried out by the entire analysis team and possibly

    members of other sections of the house, to ensure they each have a good

    understanding of what is to be expected of the system.

    ? Complete scenario based analysis

    o Identify actors

    o Create use-cases

    o Create activity diagrams

    o Create swim lane diagrams Responsibility: This will be carried out by the entire analysis team in order to

    incorporate different ideas into the system and achieve a wider scope. We will then

    compile our ideas and decide upon a particular direction to go in. In doing this, we

    will all be working with the same use-cases in mind when designing other diagrams.

    ? Complete Acceptance criteria

    o Formalise requirements Responsibility: Matthew Kavanagh

    o Identify testable criteria Responsibility: Tristan Morrison

    o Create test procedures Responsibility: Angus McAlpine

    ? Complete class based analysis

    o Identify classes

    o Design class diagrams Responsibility: This will be done as a team, to ensure that we each have a good

    understanding of what the classes are, which will in turn allow us to create the

    remaining diagrams individually

    o Create CRC cards Responsibility: Stefan Pearson

    o Create collaboration diagrams Responsibility: Danielle Hamilton

    ? Complete behaviour based analysis

    o Create State diagrams Responsibility: Kyle Truswell

    o Create Sequence diagrams Responsibility: Danielle Hamilton

    ? Complete flow based analysis

    o Create data flow diagrams Responsibility: Stefan Pearson

    o Create control flow diagrams Responsibility: Kyle Truswell

    o Write processing narrative Responsibility: Danielle Hamilton

    ? Complete Requirements specification

    o Compile and explain diagrams Responsibility: Entire team

Design

    Milestones

    The Design stage has 2 major milestones:

    1. Complete High-level design specification

    2. Create Low-level design specification

    3. Complete Test specification

    4. Complete Manual page

    Tasks

    ? Complete High-level design specification

    o Complete architectural design Responsibility: Entire team

    o Complete common tactical policies Responsibility: Robert Stanley

    o Complete requirements cross reference

    Responsibility: Jairo Kasmierchcki

    ? Complete Low-level design specification Responsibility: Entire team

    ? Complete detailed design

    Responsibility: Entire team

    ? Complete test specification

    o Define Scope

    Responsibility: Angus McAlpine

    o Create Test plan

    Responsibility: Tristan Morrison

    o Establish Test procedures

    Responsibility: Matthew Kavanagh

    ? Complete Manual page

    Responsibility: Jairo Kasmierchcki

    Coding

    Milestones

    The Coding stage has 2 major milestones:

    1. Create the structure of the program

    2. Create the content of the program

    Tasks

    ? Establish interface between classes

    ? Create the groups of classes separately

    Responsibility: Entire team Each person in the team will write the code for one group of classes (assuming there

    are three groups of classes) or what works out to be roughly 33% of the classes.

    ? Use groups of classes together as one program

    Responsibility: Entire team

Each person's group(s) of classes will be combined to create one program.

Testing

    Milestones

    The Testing stage has 1 major milestone:

    1. Carry out test specification

    Tasks

    • Carry out test specification

    o Carry out test procedures from acceptance criteria Responsibility: Matthew Kavanagh

    o Carry out test procedures from test specification Responsibility: All Quality Assurance team members, subdivided along logical lines.

Delivery

    Milestones

    The Delivery stage has 2 major milestones:

    1. Create the installation guide

    2. Create the user guide

    Responsibilities: Entire team

    The user guide and installation guide will be written by the entire team. At a later

    date, specific parts of the writing process may be assigned to individual members.

    HTML Renderer

    1. Requirements Analysis 2. Design 3. Coding 4. Testing 5. Delivery

    1.1 Establish requirements 2.1 High level design 3.1 Structure of program 4.1 Perform Tests 5.1 User guide

    1.2 Complete Scenario 2.1.1 Architectural Design 3.2 Content of program 5.2 Installation guide analysis

    1.2.1 Draw Use case diagrams 2.1.2 Common tactical policies

1.2.2 Create Activity diagrams 2.1.3 Requirements cross-reference

1.2.3 Create Swim lanes 2.2 Low level design

    1.3 Acceptance criteria 2.3 Test Specification

     2.3.1 Architectural Design 1.4 Complete Class analysis

    2.3.2 Architectural Design 1.4.1 Define Class diagrams 2.3.3 Architectural Design 1.4.2 Create CRC cards 2.4 Manual Page

     1.4.3 Create collaboration diagrams

     1.5 Complete Behaviour

    analysis

    1.5.1 Create State diagrams This is the Work Breakdown Structure for the project. It shows how the

    tasks are broken down into tasks throughout the phases of the project: 1.5.2 Create Sequence diagrams

    Analysis 1.6 Complete Flow analysis Design

    Coding 1.6.1 Create Data flow diagram Testing

    Delivery 1.6.2 Create Control flow

    diagram

1.6.3 Write Processing narrative

Milestone and task list

Analysis

     Establish customer requirements

     Complete Scenario based analysis

     Create Use-Cases

     Create Activity diagrams

     Create Swim Lane diagrams

     Create Acceptance criteria

    Formalise requirements

    Identify testable criteria

    Create test procedures

    Complete Class based analysis

     Identify Classes

     Create Class diagrams

     Create CRC cards

     Create Collaboration diagrams

     Complete Behaviour based analysis

     Create Sequence diagrams

     Create State diagrams

     Complete Flow based analysis

     Create Data flow diagrams

     Create Control flow diagrams

     Write processing narrative Complete Analysis

Design

     High-level design

     Architectural design

     Requirements cross-reference

     Common tactical policy

     Low-level design

     Class/Object diagrams

     Activity diagrams

     Diagram Integration

    Test specification

    Manual Page

    Complete Design

Programming

     Create structure of program

     Create content of program Complete programming

Testing

     Perform testing

Complete Testing

Delivery

     Create User guide

     Create Installation guide

     Audit all documentation Complete Project

Report this document

For any questions or suggestions please email
cust-service@docsford.com