DOC PREVIEW
PSU CSE 420W - Individual Project

This preview shows page 1-2 out of 7 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 7 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 7 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 7 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Project TitleCSE420W Team ProjectHappy StudentFall, 2006Pennsylvania State UniversityTable of Contents1. Abstract2. Requirements2.1. Background2.2. Essential Solution2.3. Environment2.4. Implementation Outline2.5. Operational Assumptions3. Technical Specification3.1. Development Tools & Languages3.2. Design / Architecture3.2.1. Design Decomposition (Modules, Entities, Components)3.2.2. Data Formats, Interfaces3.2.3. UML Diagrams, Flow Charts, State Diagrams, etc.3.3. Testable Quality Requirements4. Standards5. Test Plan6. QA Plan7. Deployment Plan8. Maintenance Plan9. Team Organization10.Schedule11.Project Cost1 AbstractDescribe project purpose & scope including relevant benefits, objectives and goals (1 page).2 Requirements2.1 BackgroundState relevant background information, rationale for development, and define terms if necessary.2.2 Essential SolutionDescribe the process steps your software is going to automate in plain English, give as much detail as possible. You must list all functions the software is going to perform including the expected input and output. Prioritize functionality as necessary. You may define subsections as necessary. This should be the main bulk of your requirement document.2.3 EnvironmentList hardware and software requirements for the software; provide concrete numbers and third party software version information.2.4 Implementation OutlineIf a particular implementation is suggested by customer outline it here.2.5 Operational AssumptionsList all conditions you take for granted. Highlight conditions (e.g. environmental changes, version conflicts, etc.) that would interfere or break your software. Indicate whatcircumstances would result in requirement reevaluation.3 Technical SpecificationTechnical specification must restate Essential Solution in technical terms filling in all the blanks on how each function is going to be implemented and how each problem posed in requirements document is solved. Ideal specification should neither require knowledge ofthe project’s background nor should require any process-wide thinking on coder’s part.3.1 Development Tools & LanguagesState which development tools, languages, libraries, coding standards and software development methodologies shall be used.3.2 DesignChoose design decomposition, identify entities or modules. Provide high-level design (i.e. architecture) of the proposed solution. Include UML or other visual diagrams as necessary.Create subsections for each design component (i.e. module, entity or class). Perform detailed design for design component; include state or event diagrams, flow charts, entity-relationship diagrams as necessary. List interface, event, function definitions including their parameters; specify data formats.3.3 Quality RequirementsList testable quality requirements providing concrete numbers for verification.4 StandardsAlthough you might have mentioned this in spec list all important standards you are required to follow or enforce. E.g. Web Services implementation must adhere to WSI 1.0,C code must be portable and adhere to ANSI C / C99, etc.5 Test PlanOutline your test strategy, which may include unit testing, standard compliance testing, integration testing, system testing, load testing, and user acceptance testing.6 QA PlanOutline what actions you are going to test to ensure quality of software. This may includecode reviews, beta testing, nightly builds with error reporting, etc.7 Deployment PlanOnce the software development is finished the software must be packaged and deployed. Describe how you are going to handle deployment, what are the target system requirements or potential problems.8 Maintenance PlanSpecify how you are going to maintain the software once it has been deployed or released. You should detail your support, bug tracking and update processes.9 Team OrganizationCome up with a team structure for the project. List team members and their roles.10 ScheduleGiven the team structure you came up with create a Gantt chart of development activities starting from coding effort launch, going through testing and culminating with deployment.11 Project CostEstimate software development cost given your team organization and schedule. Include pessimistic, optimistic and most likely estimates. Also include an estimate of maintenance & support costs. Given this figures determine cost-savings benefits of your


View Full Document

PSU CSE 420W - Individual Project

Download Individual Project
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Individual Project and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Individual Project 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?