Project Summary

Mission and Scope

TODO: Answer these questions in your own words. The sample text can help give you some ideas on what to write and how to write it.
What business problem does this project address?
There is a need for businesses to set up their own on-line store as rapidly and easily as possible. Virtually every business has customers that prefer to purchase on-line, but few businesses have the expertise or time to create an e-commerce site themselves. Custom-coded e-commerce sites also usually lack the advanced features found on big shopping sites, and may contain defects and security holes.
Active investors need constant awareness of market conditions and the state of their stock portfolio. Decisions to trade stocks are based on company financial data, company news, industry news, economic indicators, and simulation models. It is difficult for people to gather and consider all of the needed information when working under time pressure.
What is the goal of this project?
The goal of this project is to build an e-commerce website engine that is widely reusable by small- to medium-sized businesses, full featured, and easy to use and administer. Our customers will be able to set up their own e-commerce site that looks like the most popular, big shopping sites.
We will build a completely new stock trading application with novel features to help traders make better decisions. In addition to all the standard features that users expect, we will add powerful visualization, simulation, and news aggregation features. We expect that our application will become the preferred trading platform for private U.S. investors who trade more than ten different stocks per day.
What is the scope of this project?
We will build an e-commerce engine with a set of features similar those found on the most popular shopping sites. Our shopping sites will scale up to a fit the needs of active small businesses with a few thousand concurrent shoppers.
We will build a new client application that will use existing back-end servers to execute trades and gather data from several sources. The client will provide normal trading features and emphasize three new feature areas: visualization, simulation, and news aggregation.

Status

TODO: Briefly describe the status of this project. E.g., what phase are you in? And, what is your next major milestone? Detailed project status is written in the status reports, not here.

We have completed our second internal release and are currently working on adding more of the functionality described in our product specification and fixing defects.

The next major milestone is a third internal release with nearly complete functionality and a wider set of testers.

Status reports:

Resources and Schedule

TODO: Briefly describe the project resources and schedule. This is condensed from the project plan, resource needs, and legal issues templates. See those templates for reusable sample answers.
What are the deadlines for this project?
  • Start: Project proposal approved by management
  • Kickoff + 30 days: Detailed SRS finished, reviewed, and approved
  • Kickoff + 90 days: Design and initial implementation
  • Kickoff + 120 days: First release to QA department
  • Kickoff + 180 days: Release 1.0.0
  • Jun 1st: SRS ready for review
  • Aug 1st: Release 0.7.0
  • Sep 1st: Release 0.8.0
  • Oct 1st: Release 0.9.0
  • Dec 1st: Release 1.0.0 RC1
  • DATE: MILESTONE
  • DATE: MILESTONE
  • DATE: MILESTONE
  • DATE: RELEASE-NUMBER
Who is working on this project?
  • 100% PERSON-NAME
  • 100% PERSON-NAME
  • 75% PERSON-NAME
  • 33% PERSON-NAME
What capital resources are allocated to this project?
  • Hardware: 3 new servers and 1 low-end load balancer
  • Software licenses: 1 production database server license
  • Facilities: No new facilities
  • HARDWARE
  • SOFTWARE LICENSE
  • FACILITIES
What are the main legal concerns for this project?
  • Intellectual property: our new e-commerce engine product can be protected with standard software licensing contracts.
  • Privacy and security: we must satisfy the criteria for an industry certification.
  • Government regulations: our e-commerce engine will help our customers comply with sales tax collection law.
  • Potential harm: we must include features that prevent abuse, e.g., fraudulent product returns.
  • Intellectual property: DESCRIPTION
  • Privacy and security: DESCRIPTION
  • Government regulations: DESCRIPTION
  • Potential harm: DESCRIPTION

Requirements

TODO: Briefly describe the most important system requirements. This is condensed from the user needs, interview notes, SRS, use case suite, and feature set documents. Use either the links to separate use case and feature specification documents, or the more detailed bullet lists on this page.
Who are the project stakeholders?
  • PROJECT CHAMPION / EXECUTIVE SPONSOR
  • DEPARTMENTS WITHIN YOUR COMPANY
  • CORPORATE PARTNERS
  • KEY CUSTOMERS
What user needs have you gathered?
What are the requirements specifications?
What are the use cases for this system?
What are the feature specifications for this system?
What are the non-functional requirements?
  • USABILITY-REQUIREMENTS
  • RELIABILITY-REQUIREMENTS
  • SECURITY-REQUIREMENTS
  • PERFORMANCE-REQUIREMENTS
  • SCALABILITY-REQUIREMENTS
  • MAINTAINABILITY-REQUIREMENTS
  • INTEGRATION-REQUIREMENTS
  • INTERNATIONALIZATION-REQUIREMENTS
  • SUPPORTABILITY-REQUIREMENTS
  • BUSINESS-LIFE-CYCLE-REQUIREMENTS
What are the environmental requirements?
  • HARDWARE-COMPATIBILITY-REQUIREMENTS
  • SOFTWARE-COMPATIBILITY-REQUIREMENTS
  • API-REQUIREMENTS
  • IMPORT-EXPORT-REQUIREMENTS

Design

TODO: Briefly describe the most important aspects of the design. This is condensed from the design template and associated worksheets.
What are your ranked design goals?
  1. Correctness: This design correctly matches the given requirements.
  2. Feasibility: This design can be implemented and tested with the planned amount of time and effort.
  3. Understandability: Developers can understand this design and correctly implement it.
  4. Implementation phase guidance: This design divides the implementation into components or aspects that can correspond to reasonable implementation tasks.
  5. Modularity: Concerns are clearly separated so that the impact of most design changes would be limited to only one or a few modules.
  6. Extensibility: New features can be easily added later.
  7. Testability: It is easy to test components of this design independently, and information is available to help diagnose defects.
  8. Efficiency: The design enables the system to perform functions with an acceptable amount of time, storage space, bandwidth, and other resources.
Where are your design documents?

Quality Assurance

TODO: Briefly describe your quality goals and how you will achieve them. This is condensed from the QA plan, test suite, and test cases documents.
What are your ranked quality goals?
  1. Correctness
  2. Robustness
  3. Accuracy
  4. Compatibility
  5. Usability
  6. Security
  7. Reliability
  8. Scalability
  9. Operability
  10. Maintainability
What QA activities will you use?
  • Preconditions and assertions
  • Buddy reviews
  • Review meetings
  • Unit testing
  • System testing
Where are the test cases?

Packaging, Delivery, and Deployment

Where is the release checklist or sign-off document?
Release checklist
How is the product packaged and deployed?
How is the product installed?
  • System requirements: DESCRIPTION
  • STEP
  • STEP
  • STEP

User Support

Where is the user documentation?
How can users get technical support or report problems?
  • Support: DESCRIPTION
  • Issue tracking: DESCRIPTION

Glossary

TODO: Define any technical terms that you use above, if a new member of the team would not already know them. This is condensed from the glossary documents.

Project-specific terms for this project are below. See also, standard terms.

Order-line
n. One line on a customer order, consisting of a product name, price, and quantity.
Product
n. An item from the product catalog offered for sale on a shopping site. Each product has a unique SKU number, name, description, and regular price.
Product catalog
n. A database of all products offered for sale on a shopping site.
PROJECT-SPECIFIC TERM
DEFINITION
TODO: Check for words of wisdom for additional advice on this template.
Company Proprietary
Copyright © 2003-2004 Method Labs. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.