Project Planning Report - 학생 관리 시스템 (통합 계획서)

소개

이번 리포트는 Software Project Management 수업때 마지막 통합 assignment였으며, 학생 관리 시스템을 제작하기 위하여 어떻게 Project Planning Report안에 들어갈 모든 내용을 수집,관리,실행하는지를 it skill과 접목하여 만들었습니다. 유즈케이스부터 코코모 모델, ms 프로젝트를 이용한 gantt chart, pert chart등등 총 100장이 넘어가는 방대한 리포트입니다. 영국대학 재학시 만들었기에 외국유학을 생각하시고 있으시거나 혹은 현재 외국에서 유학을 시작하시는 분들께서는 어떤식으로 과제가 학생들에게 나가고 어떤식으로 작성하여 제출하는지에 대한 가이드 역할을 충분히 할 수 있는 리포트라 생각이 됩니다.

100% course work 수업이라 더더욱 신경썼던 리포트이구요. 좋은 성적을 받아서 장학금을 신청했던 semester에 썼던 리포트입니다~~

목차

1.INTRODUCTION
1.1Current Environment
1.1.1Business Requirements
1.1.2Functional Requirements
1.1.3User Requirements
1.2Project Goal and Objectives
1.2.1Project Goal
1.2.2The Main Purposes of the SDevMOP system for Oxford University
1.2.3The Sub Purposes of the SDevMOP system for Oxford University
1.2.4The Objects for the each SDevMOP system function
1.3User Groups
1.4Product Overview
1.5Project Scope
1.6Major Milestones

2.PROJECT ORGANIZATION
2.1Development Process Model
2.1.1Development Environment
2.1.2Installation and Undertake
2.1.3Work Breakdown Structure
2.1.4Interfaces
2.1.5Network Diagram
2.2Project team, roles, and responsibilities
2.2.1Project Team
2.2.2Roles and Responsibilities

3.MANAGEMENT APPROACH
3.1Management Priorities
3.2Project Tracking and Control
3.2.1Status Reporting
3.2.2Stage Exits (Project Checkpoints)
3.3Assumptions, Constraints, and Dependencies
3.3.1Assumptions and Dependencies
3.3.2Constraints
3.4Risk Management
3.4.1Project Risks
3.4.2Technical Risks
3.4.3Business Risks
3.4.4Known Riss
3.4.5Predictable / Unpredictable Risks
3.4.6Technology Risks
3.5Project Estimates
3.5.1Size Estimates
3.5.2Time Estimates
3.6Staffing Plan
3.6.1Requirement Skills
3.7Master Schedule/Project Deliverables

4.TECHNICAL APPROACH
4.1Programming Languages
4.1.1Development techniques
4.1.2Tools
4.2Security
4.3Hardware/Software Requirement
4.4Configuration Management
4.4.1Configuration management tools
4.4.2Configuration identification method
4.4.3Configuration control method
4.4.4Status accounting method
4.4.5Evaluation method
4.4.6Release management method
4.4.7Procedure for baselining a work product
4.5Change Control Process
4.6Testing Strategy
4.6.1Software Testing
4.6.2Unit Testing
4.6.3Integration Testing
4.6.4System Testing
4.7Quality Assurance
4.7.1Scope
4.7.2Reviews
4.7.3Audits
4.7.4Risk Management
4.8Defect Prevention
4.9Training
4.10Documentation

5.REFERENCE

본문내용

1. INTRODUCTION
1.1 Current Environment
This Student Management System project named SDevMOP is completely based on Oxford University College in UK.
The Oxford University College is one of the largest private education providers in UK, which is a major international university with over 5,000 students full-time. Nevertheless, they have partially computerized procedures in Student Management System, which is uncomfortable for large service units in Oxford University College and students.
In order to overcome the management and administrative difficulties, Oxford University desired to implement a Student Management System. The systems would be implemented on a Local Area Network with in Oxford University and Wide Area Network, so as to replace the existing manual paper based system.
The main point of the new systems would be a graphical user interface in order to create the user friendly design and to enable the existing staffs and students to utilize the system with minimal training.

참고자료

· 1. Wiegers, Karl E. 2003, Software Requirements 2: Practical techniques for gathering and managing requirements throughout the product development cycle, 2nd ed., Redmond: Microsoft Press.
· 2. Robert T. Futrell, Donald F. Shafer, Linda Isabell Shafer. 2002, Quality Software Project Management ,
· Prentice Hall PTR.
· 3. Pankaj Jalote. 2002, Software Project Management in Practice , Addison-Wesley.
· 4. Andrew Stellman, Jennifer Greene. 2005, Applied Software Project Management, Oreilly & Associates Inc.
· 5. Jeffrey O. Grady. September 2005, Systems Requirement Analysis-WHAT IS SYSTEM REQUIREMENTS ANALYSIS?, Academic Press.
· 6. Boehm, B. 2000, “"Software Estimation Perspectives,”" IEEE Software. IEEE, Cupertino, CA.
· 7. Nazim H. Madhavji, M. M. Lehmann, J. Ramil. 2005, Software Evolution And Feedback (Theory And Practice) , John Wiley & Sons Inc.
· 8. Markus Vvlter, Thomas Stahl, Jorn Bettin . 2006, Model-Driven Software Development: Technology, Engineering, Management, WILEY.
· 9. Thayer, Richard H. (EDT)/ Dorfman, Merlin (EDT). 2005, Software Engineering (The Supporting Processes), John Wiley & Sons Inc.
· 10. Neto, J.S.M. Mar 2000. ntegrando Requisitos Não Funcionais ao Modelo de Objetos, M.Sc. Dissertation at PUC-Rio.