CSCI 300/600
Project
The
project for this class gives students an opportunity to analyze and provide
solutions for some actual problem.
This is a team project.
Students may select their own teams which are to be no larger than three
people.
Each team should have at least one graduate student.
The project will consist of a problem identified by the team in a real
environment that the team would like to see corrected.
It should be sufficiently complex to require in-depth analysis, but
sufficiently simple to handle in the time remaining for this course.
The
project will follow the phases of system analysis and design presented in the
textbook. During the project students will produce the requested deliverables for each phase. There will be three deliverables for the project; 1) Planning Phase Report, 2) Analysis Phase
Report, and 3) Implementation Phase Report. Along
with the required deliverable, the graduate student(s) from the groups are
responsible for presenting the work of the group up to that
point. Each presentation is to cover the material discussed in class which
pertains to that deliverable.
An
outline for each of the required reports is
provided below.
10
% of the grade for the project will be determined by the Team
Evaluation Forms. Each student is to individually complete a team
evaluation form and submit it at the same time the final deliverable is
submitted. This form should not, however, be included as part of the final
deliverable.
Planning
Phase Report
1 Executive Summary
2 Project Request
3 Feasibility Analysis
3.1 Technical
Feasibility
3.2 Economic
Feasibility
3.3
Organizational Feasibility
4 Work Plan and Staffing Plan
5 Charter and Standards
6 Risk Analysis
7 Recommendations
Analysis
Phase Report
1 Changes to Planning Phase
2 Executive Summary
3 Analysis Strategy
4 Analysis Plan
5 Information Gathering Plan
5.1 Plan overview
5.2 Interview Schedule
5.3 Interview questions
5.4 Interview transcripts
5.5 Questionnaires
5.6 Observation
5.7 Other (Name the section)
6 As-Is-System
6.1 As-Is System Overview
6.2 Use Cases
6.2.1 Use Case Overview
6.2.2 Use Case Descriptions
6.2.3 Use Case Diagrams
6.3 Structural Modeling
6.3.1 Structural Modeling Overview
6.3.2 Class-Responsibility-Collaboration Cards
6.3.3 Class Diagrams
6.4 Behavioral Modeling
6.4.1 Behavioral Modeling Overview
6.4.2 Sequence Diagrams
6.4.3 Collaboration Diagrams
6.4.4 Statechart Diagram
7 To-Be System
7.1 To-Be System Overview
7.2 Use Cases
7.2.1 Use Case Overview
7.2.2 Use Case Descriptions
7.2.3 Use Case Diagrams
7.3 Structural Modeling
7.3.1 Structural Modeling Overview
7.3.2 Class-Responsibility-Collaboration Cards
7.3.3 Class Diagrams
7.4 Behavioral Modeling
7.4.1 Behavioral Modeling Overview
7.4.1 Sequence Diagrams
7.4.3 Collaboration Diagrams
7.4.4 Statechart Diagram
Design
Phase Report
1
Changes to Planning and Analysis Phases
2 Packages and Package Diagrams
3 Revised Use Cases
4 Revised Structural Models
5 Revised Behavioral Models
6 Design Strategy
6.1 In House
6.2
Packaged Software
6.3
Outsourcing
6.4 Recommendation
7
System Architecture
7.1 Current System Architecture
7.2
To-Be System Architecture
8
Network Model
8.1 Current Network Model
8.2
To-Be System Network Model
9
Hardware and Software Specification
9.1 Current Hardware and Software
9.2
To-Be System Hardware and Software
10
Global Issues
11 Security
12 User Interface Structure
12.1 Use scenarios
12.2
User Interface Structure Design
12.3
User Interface Standards
12.4
User Interface Evaluation
13
User Interface Templates
14 Object Persistence Design
15 Class and Method Design
Implementation
Phase Report
1 Assigning programmers
2 Coordinating activities
3 Managing the Schedule
4 Testing
4.1 Unit
Tests
4.2
Integration Tests
4.3 System
Tests
4.4
Acceptance Tests
5 Documentation
6 Installation
6.1
Conversion
6.2 Change
Management
7 System Support
8 System Maintenance
9 Project Assessment Criteria