Assignment 3 Software Engineering
SOFTWARE ENGINEERING
ASSIGNMENT 3 BIT 302
FINAL DOCUMENT
PROJECT NAME: DEFENSE YOUR CASTLE
STUDENT ID:
E1100248
E1200250
Contents
1. Project Plan 5
1.1. Project Introduction 5
1.2. Project Goal 5
1.3. Project Objectives 5
1.4. Project Scope 5
2. Resource Allocation 6
2.1. Minimum hardware & software requirements 6
2.2. Required Data and Information 6
3. Project Standards & Procedure 7
3.1. Proposed Systems Development Methodology 7
3.2. Requirement Analysis 7
3.3. Design 7
4. Deliverables and Milestones 8
4.1. Project Deliverables: 8
4.2. Milestones: 8
5. Project Team Organization 9
6. Project Schedule 10
6.1. Gantt Chart 10
6.2. Work Breakdown Structure (WBS) 11 11
6.3. Risk Management Plan 12
6.3.1. Objective 12
6.3.2. Process 12
6.3.3. Risk Identification 12
6.3.4. Methods for Risk Identification 12
6.3.5. Risk Analysis 13
6.3.6. Risk Response Planning 13
7. Software Requirement Definition Document 14
7.1. Introduction 14
7.2. Purpose 14
7.3. Scope 14
7.4. Functional Requirement 14
7.5. Non-Functional Requirements 15
7.5.1. External User Interface Requirements 15
7.5.2. Performance Requirements 15
7.5.3. Design Constraints 15
7.5.4. Quality Attributes 16
7.6. Definition/abbreviation 16
7.7. References 17
7.8. Use Case Diagram 17
8. Software Design Specification 21
8.1. High-Level Design 21
8.2. Class Diagram 22
8.3. Sequence Diagram 23
8.4. Interface Design 24
9. Data Design 25
10. Test Objectives 26
11. Test Plan 26
11.1. Purpose: 26
11.2. Team Organization 26
11.2.1. Testing Team: 26
11.2.2. Developer Team 27
11.3. References 27
11.4. Test Items 27
11.5. Features to be tested 27
11.6. Features not to be tested 28
11.7. Approach 28
11.8. Test Deliverables 28
11.9. Test Environment 28
11.9.1. Hardware 28
11.9.2. Software 28
11.9.3. Tester 28
11.9.4. Testing Tools 29
11.10. Item Pass/Fail Criteria 29
11.11. Exit Criteria 29
11.12. Scheduling 29
12. Test Method 29
12.1. Test Objective 29
12.1.1. Unit Test 29
12.1.2. Integration Test 29
12.1.3. System
ASSIGNMENT 3 BIT 302
FINAL DOCUMENT
PROJECT NAME: DEFENSE YOUR CASTLE
STUDENT ID:
E1100248
E1200250
Contents
1. Project Plan 5
1.1. Project Introduction 5
1.2. Project Goal 5
1.3. Project Objectives 5
1.4. Project Scope 5
2. Resource Allocation 6
2.1. Minimum hardware & software requirements 6
2.2. Required Data and Information 6
3. Project Standards & Procedure 7
3.1. Proposed Systems Development Methodology 7
3.2. Requirement Analysis 7
3.3. Design 7
4. Deliverables and Milestones 8
4.1. Project Deliverables: 8
4.2. Milestones: 8
5. Project Team Organization 9
6. Project Schedule 10
6.1. Gantt Chart 10
6.2. Work Breakdown Structure (WBS) 11 11
6.3. Risk Management Plan 12
6.3.1. Objective 12
6.3.2. Process 12
6.3.3. Risk Identification 12
6.3.4. Methods for Risk Identification 12
6.3.5. Risk Analysis 13
6.3.6. Risk Response Planning 13
7. Software Requirement Definition Document 14
7.1. Introduction 14
7.2. Purpose 14
7.3. Scope 14
7.4. Functional Requirement 14
7.5. Non-Functional Requirements 15
7.5.1. External User Interface Requirements 15
7.5.2. Performance Requirements 15
7.5.3. Design Constraints 15
7.5.4. Quality Attributes 16
7.6. Definition/abbreviation 16
7.7. References 17
7.8. Use Case Diagram 17
8. Software Design Specification 21
8.1. High-Level Design 21
8.2. Class Diagram 22
8.3. Sequence Diagram 23
8.4. Interface Design 24
9. Data Design 25
10. Test Objectives 26
11. Test Plan 26
11.1. Purpose: 26
11.2. Team Organization 26
11.2.1. Testing Team: 26
11.2.2. Developer Team 27
11.3. References 27
11.4. Test Items 27
11.5. Features to be tested 27
11.6. Features not to be tested 28
11.7. Approach 28
11.8. Test Deliverables 28
11.9. Test Environment 28
11.9.1. Hardware 28
11.9.2. Software 28
11.9.3. Tester 28
11.9.4. Testing Tools 29
11.10. Item Pass/Fail Criteria 29
11.11. Exit Criteria 29
11.12. Scheduling 29
12. Test Method 29
12.1. Test Objective 29
12.1.1. Unit Test 29
12.1.2. Integration Test 29
12.1.3. System