Dashboard > SportsForge > Home > Requirements > Information > Page Comparison
Requirements
compared with
Current by Ted Husted
on Aug 30, 2006 06:30.

(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 7 changes. View first change.

 "The hardest part of building a software system is deciding precisely what to build." -- Frederick Brooks.
  
 h2. Chapter 1. Purpose and Scope
  
 (/) Scroll down or click a link.
  
 || [1a.|#Mission]| What is the overall scope and goal? What is our mission statement? |
 || [1b.|#Stakeholders]| Who are the Stakeholders? (Who cares if we build the system or not?) |
 || [1c.|#Topics]| What topics are within our scope? What topics are out of scope? |
  
 h2. Chapter 2. [Terms Used / Glossary|Use Cases#UseCases-BusinessUseCases]
  
 h2. Chapter 3. [Use Cases]
  
 || [3a.|Use Cases#UseCases-Actors] | The "actors" involved in the system under design |
 || [3b.|Use Cases#UseCases-BusinessUseCases] | The business use cases (operations concepts) |
 || [3c.|Use Cases#UseCases-SystemUseCases] | The system use cases (development concepts) |
  
 h2. Chapter 4. The Technology Used
  
 || [4a.|#Technology] | What technology requirements are there for this system? |
 || [4b.|#Systems] | With what systems will this system interface? What are the interface requirements? |
  
 h2. Chapter 5. Other requirements
  
 || [5a|#Process]. | Development process |
 | | Q1. Who are the project participants? |
 | | Q2. What values will be reflected? (Simple, soon, fast, or flexible?) |
 | | Q3. What feedback or project visibility do the users and sponsors expect? |
 | | Q4. What can we import? What must we build? What other systems have a similar scope? |
 | | Q5. Under what other process requirements does the project operate? |
 || [5b.|#Rules] | Business Rules
 || [5c.|#Peformance] | Performance
 || [5d.|#Operations] | Operations, security, documentation
 || [5e.|#Usability] | Use and usability
 || [5f.|#Maintenance]| Maintenance and portability
 || [5g.|#Deferred] | Unresolved or deferred
  
{info} The outline for this "plausible requirements" document was adapted from [Writing Effective Use Cases|http://www.amazon.com/exec/obidos/tg/detail/-/0201702258/apachesoftwar-20/], pages 13-14. {info}
  
 ----
  
 {anchor:Mission }
 h3. Mission
  
 (1a.) What is the overall scope and goal? What is our mission statement?
  
 ||Scope | Internet application that can be used to track a sports team, league or section. |
 ||Goal| Present detailed information about youth sports teams and atheletes, including scores, news, standings, and statistics. The presentation must be easy to navigate and available to the widest possible audience. In short, the appication provides the tools to create a local "ESPN.com" for a youth sports team, league, or section. |
 ||Mission Statement | The SportsForge software exists to fill the gaps of reporting on youth sports at a local and high school level. By providing information about youth sports teams, leagues or sections, we help bring communities, parents, and youth atheletes closer together. We encourage non-athlete students to become involved by providing the opportunity to conduct interviews and write stories to be publishd on a SportsForge website. |
  
 {anchor:Stakeholders }
 h4. Stakeholders
  
 (1b.) Who are the Stakeholders? (Who cares if we build the system or not?)
  
 || Stakeholder || Rationale |
 | (!) ... | |
  
 {anchor:Topics }
 h3. Topics
  
 (1c.) What topics are within our scope? What topics are out of scope?
  
 ||In/Out of Scope ||Topic |
 || (on) | (!) ... |
 || (off) | (!) ... |
 | | (!) ... |
  
----
  
 {excerpt-include:Use Cases|nopanel=true}
  
----
  
 {anchor:Technology}
 h3. Technology
  
 (4a.) What technology requirements are there for this system?
  
 * Java API 1.5
 * Servlet API 2.3
 * HTTP 1.1
 * HTML 4
 * JavaScript/ECMAScript
 * Struts 2
 * MySQL 5 or equivalent
  
 {anchor:Systems}
 h3. Systems
  
 (4b.) With what systems will this system interface? What are the interface requirements?
  
 * HTTP/HTML (web browsers)
 * RSS and Atom (news feeds)
 * SQL DBMS (MySQL)
  
----
  
 {anchor:Process }
 h3. Development process
  
 (5a.) The development process outlines the nuts and bolts of the project.
  
 _Who are the project participants?_
  
 * Jeff Wellings
 * Ted Husted
* Toby Jee
 * Other interested parties
  
 _What values will be reflected? (Simple, soon, fast, or flexible?)_
  
 Simple and flexible.
  
 _What feedback or project visibility do the users and sponsors expect?_
  
 The project is expected to be transparent. All development decisions are expected to take place in public forums.
  
 _What can we import? What must we build? What other systems have a similar scope?_
  
 *Import*
 * Linux or Windows
 * Java 1.5
 * Tomcat 5.5 Web Container
 * Struts 2 Web MVC Framework
 * iBATIS Data Access Framework
 * MySQL Database System
 * JUnit
 * [DbUnit|http://dbunit.sourceforge.net/]
 * [Web testing solution|http://www.junit.org/news/extension/web/index.htm#watij] (e.g. Web Canoo, [HostedQA|http://www.autoriginate.com/] or maybe [FITnesse|http://fitnesse.org/])
 * The original [SectionXSports|http://svn.sourceforge.net/viewcvs.cgi/struts/SportsForge/] codebase, migrated to Struts 2.
 * SectionXSports data schema
  
 *Build*
 * Requirements and use cases
 * Struts configuration
 * Server Pages (adapt from v1)
 * iBATIS configuration
 * Database queries (adapt from v1)
 * Development database with realistic test data (have schema from v1)
 * Unit tests against Action classes and database queries
 * Integration tests against user interface (web browser)
  
 *Systems with a similar scope*
 * [Club Express|http://www.clubexpress.com/]
 * [ESPN|http://espn.go.com/] "SportsForge is ESPN for youth sports."
 * [eTeamz|http://eteamz.active.com/index.cfm?] ([Working example|http://fairportpackers.org/])
 * *[SectionXSports|http://sectionxsports.com/]*
 * [Youth and High School Web Sites|http://dmoz.org/Sports/Youth_and_High_School/]
  
 _Under what other process requirements does the project operate?_
  
 Code and other intellectual property donated to SportsForge will be distributed under the [Apache License|http://apache.org/licenses/].
  
 {anchor:Rules}
 h4. Business Rules
  
 (!) (5b.) ...
  
 {anchor:Performance}
 h4. Performance
  
 (!) (5b.) ...
  
 {anchor:Operations}
 h4. Operations, security, documentation
  
 (!) (5d.) ...
  
 {anchor:Usability}
 h4. Use and usability
  
 (!) (5e.) ...
  
 {anchor:Maintenance }
 h4. Maintenance and portability
  
 (!) (5f.) ...
  
 {anchor:Deferred}
 h4. Unresolved or deferred
  
 (!) (5g.) ...
  
 ----
  
 {info} The outline for this "plausible requirements" document was adapted from [Writing Effective Use Cases|http://www.amazon.com/exec/obidos/tg/detail/-/0201702258/apachesoftwar-20/], pages 13-14. {info}
Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators