# 1 Introduction

## 1.1 Purpose
Define and update the requirements for the Get Real website (http://getreal.ous.edu) and associated support pages for Version 2 (Rev2), succeeding Version 1 (Rev1, circa summer 2006). The website’s purpose is to attract and encourage Oregon high school students to pursue coursework leading toward a baccalaureate degree in computer science (CS) at Oregon University System (OUS) campuses.

## 1.2 Scope
- Product name: Get Real website (getreal.ous.edu), Version 2.
- What it will do:
  - Provide teen-friendly, easy-to-navigate web content about CS careers, education pathways, and resources.
  - Offer sections including exploring colleges, jobs and earnings, real people profiles (including women in computing), resources, articles, and new features such as search, RSS feeds, an FAQ, and guidance on high school courses and CS minors.
- Application, benefits, objectives, goals:
  - Encourage more Oregon students to choose CS and related majors, ultimately increasing CS graduates from Oregon universities.
  - Benefits include personal and career information from CS professionals; CS course and campus information; timely updates (e.g., Q&A); and actionable plans to prepare for a CS career.
- Consistency with higher-level specifications: [N/A]

## 1.3 Product overview

### 1.3.1 Product perspective
The product is an update of the existing Get Real website (Version 1), to be deployed as Version 2 within the OUS domain and hosted on OSU servers. A future Version 3 may be needed.

- System interfaces
  - The website operates as an extension of the OUS site (getreal.ous.edu) to leverage search engine visibility.
  - Interfaces to OUS policies and conventions for copyright and security.
  - [N/A] for additional system-to-system interfaces.

- User interfaces
  - The site shall work and be tested against Internet Explorer, Firefox, and Netscape.
  - Teen-friendly, easy-to-navigate pages with improved graphic design: more white space, images, shorter paragraphs, bullet points, charts, and avoidance of “walls of text.”
  - Use of interactive elements (e.g., interactive table menus) to provide detail while keeping main pages concise.

- Hardware interfaces
  - No special hardware interfaces. [N/A] for device-specific requirements.

- Software interfaces
  - Use of web search tools (e.g., Google) to provide internal site search and external CS-related search.
  - RSS feeds to surface selected CS information.
  - Adherence to CSS and style conventions established in Get Real Version 1.
  - Development uses Dreamweaver with check-in/out features and local site files. Versions and specifications: [N/A].

- Communications interfaces
  - No special communication interface requirements beyond standard web protocols. [N/A] for specific network protocol requirements.

- Memory constraints
  - [N/A]

- Operations
  - User-initiated browsing. No unattended operations specified.
  - Development operations include Dreamweaver check-in/out. Backup and recovery: [N/A].

- Site adaptation requirements
  - [N/A]

- Interfaces with services
  - External CS-related sites (e.g., OUS campus sites) via links.
  - RSS services for curated CS information.
  - External video content examples referenced for design inspiration.

### 1.3.2 Product functions
- Exploring College: Present CS offerings from OUS campuses and other Oregon colleges.
- Jobs & Money: Present how CS careers contribute to society and associated earnings.
- Real People: Profile recent graduates and experienced professionals using CS in diverse fields; support video or audio to convey personal messages.
- Women in Computing: Profile women in CS/engineering and link to women-focused resources and organizations.
- Resources: Present pre-college technology programs and courses for high school students.
- I’m Looking For…: Provide focused Q&A with internal links to money, people, and colleges.
- Articles: Curate links to relevant external articles (e.g., job rankings).
- High School Courses: Recommend curricula and point to OUS and other university recommendations (e.g., ACM HS curricula).
- Search: Provide internal site search and external CS-related search.
- Professional Organizations: List and link to ACM, IEEE, SIGGRAPH, and student sections.
- RSS feeds: Surface selected CS information; requires periodic editorial effort to update feed items.
- Ask a Grad or Prof – FAQ: Provide a Q&A mechanism with published answers; a blog by grads or professors may be included.
- Consider a CS Minor: Present the value of a CS minor for diverse professions.
- Analytics: Track and evaluate hits and time spent on the site to inform content, design, and navigation changes.

### 1.3.3 User characteristics
- Primary users: Oregon high school students, grades 9–12, across all Oregon high schools.
- User groups:
  - Students already interested in CS seeking concise, in-depth information.
  - College-bound students not necessarily interested in CS who may be attracted by engaging content and clear benefits.
  - Students interested in other fields (e.g., medicine, law, business, sciences) where a CS minor adds value.
- Observed preferences from student feedback on Version 1:
  - Need for updated graphic design and “Real People” content.
  - Desire for more white space, images, diagrams, charts, and easier navigation.
  - Strong preference for shorter, more readable chunks of information; aversion to “walls of text.”
  - Positive reactions to interactive/visually engaging elements (e.g., spinning globe, satellite menu; interactive tables).
  - Interest in college comparison content and structured person profiles.

### 1.3.4 Limitations
- Policies and security: Copyright and other security measures shall align with the OUS site.
- Hosting and domain: Operates under OUS domain and OSU hosting.
- Resource constraints: Limited Chancellor’s Office resources.
- Bandwidth: Constraints for video streaming.
- Space constraints: Site storage space is limited.
- Additional regulatory, audit, control, safety, or real-time requirements: [N/A]

## 1.4 Definitions
[N/A]

# 2 References
- Development practices and assets
  - Local Dreamweaver site files for Get Real website at the Capital Center. Details: [N/A]
  - Dreamweaver check-in/out feature usage. Details: [N/A]
  - Get Real Version 1 CSS and style conventions. Details: [N/A]
- Hosting and domain
  - OUS main site (www.ous.edu) for style, performance example, and policy alignment. Details: [N/A]
- Content and design examples
  - University of Washington CS “real people” videos: http://www.cs.washington.edu/education/ugrad/prospective/download.html
  - EngineerGirl: www.engineergirl.org
- Women in computing resources
  - WICS UO: www.cs.uoregon.edu/groups/wics/
  - Women in Computer Architecture resources: www.cis.upenn.edu/acg/wicarch.html
- Prototype and tools
  - Get Real prototype index page with search engine examples: getreal.ous.edu/protoindex.html
  - Google search tools for internal/external search. Details: [N/A]

# 3 Requirements

## 3.1 Functions
- Exploring College
  - The system shall present a listing of CS offerings from OUS campuses and other Oregon colleges. Scope of community/private colleges: [N/A].
- Jobs & Money
  - The system shall provide content addressing societal contribution and earnings potential for CS careers.
- Real People
  - The system shall provide profiles of recent graduates and experienced professionals in diverse fields using CS.
  - The system should support video or audio elements in profiles.
- Women in Computing
  - The system shall profile women in CS/engineering and link to relevant organizations and resources.
- Resources
  - The system shall present pre-college technology programs and courses for high school students.
- I’m Looking For…
  - The system shall provide focused questions and answers linking to internal content on money, people, and colleges.
- Articles
  - The system shall present curated links to external articles relevant to CS careers and education.
- High School Courses
  - The system shall present recommended high school curricula for students interested in CS and related careers, including links to recommendations from OUS campuses and other sources (e.g., ACM).
- Search
  - The system shall provide internal search of the Get Real site.
  - The system shall provide external search of CS-related sites and OUS campuses.
- Professional Organizations
  - The system shall list and link to ACM, IEEE, SIGGRAPH, and student sections where applicable.
- RSS Feeds
  - The system shall display selected CS-related items via RSS feeds sourced from the Chancellor’s Office daily communications distribution, with periodic editorial updates.
- Ask a Grad or Prof – FAQ
  - The system shall provide a Q&A feature to obtain feedback from OUS, and publish answers in an FAQ section.
  - Optionally, the system may provide a blog by graduates or professors on CS careers. Decision status: [N/A]
- Consider a CS Minor
  - The system shall present information about the value of a CS minor for diverse professions.
- Analytics
  - The system shall track and evaluate site hits and time spent to inform content, design, and navigation updates over time.

- Input validity checks: [N/A]
- Exact sequence of operations: [N/A]
- Responses to abnormal situations (overflow, communication facilities, hardware faults/failures, error handling/recovery): [N/A]
- Effect of parameters: [N/A]
- Relationship of outputs to inputs (I/O sequences, conversion formulas): [N/A]

## 3.2 Performance requirements
- The site shall be hosted on a server that provides adequate response time consistent with high school users’ short attention spans.
- The current OUS site (www.ous.edu) is cited as an example of acceptable response time.
- Bandwidth for video streaming is a constraint to be considered.
- Static and dynamic numerical targets: [N/A]

## 3.3 Usability requirements
- The site shall be teen-friendly and easy to navigate.
- Content shall be presented in short, readable chunks using bullets, charts, and images to avoid “walls of text.”
- Pages should make good use of white space and visual elements to improve readability and engagement.
- Interactive patterns (e.g., interactive tables) may be used to keep main pages concise while offering detail.
- The design shall be consistent with OUS site conventions.
- Supported and tested browsers include Internet Explorer, Firefox, and Netscape.
- Measurable usability criteria: [N/A]

## 3.5 Logical database requirements
[N/A]

## 3.6 Design constraints
- Hosting and domain
  - The site runs on OSU servers and within the OUS domain (getreal.ous.edu) to maximize search engine visibility.
- Standards and conventions
  - Adhere to CSS and style conventions established in Get Real Version 1.
- Tools and process
  - Use Dreamweaver with check-in/out for page development; be cautious of concurrent modifications.
- Project limitations
  - Limited Chancellor’s Office resources.
  - Space constraints.
  - Bandwidth limitations for video streaming.
- Browser compatibility
  - Work and be tested against Internet Explorer, Firefox, and Netscape.

## 3.7 Software system attributes
- Reliability: [N/A]
- Availability: [N/A]
- Security
  - Copyright and security measures shall align with the OUS site.
- Maintainability
  - Consistent adherence to OUS conventions and Get Real V1 CSS/style guidelines.
  - Use of Dreamweaver check-in/out to manage content updates.
- Portability
  - Cross-browser support for Internet Explorer, Firefox, and Netscape.
- Additional attributes (interoperability, robustness, testability, etc.): [N/A]

## 3.8 Supporting information
- Background and user research
  - Feedback from Oregon high school students on Version 1 indicated needs for updated graphic design, improved “Real People” content, shorter and more visual content, and easier navigation.
- Related sites
  - Students reported using Google, Yahoo, news.myspace.com, and sites like engineergirl.org for career information.
- Future direction
  - Version 3 may incorporate lessons from Version 2 and include a knowledge base.
- User documentation
  - There are no user documents.

# 4 Verification

## 4.1 Functions
[N/A]

## 4.2 Performance requirements
[N/A]

## 4.3 Usability requirements
- Cross-browser testing shall be performed on Internet Explorer, Firefox, and Netscape.

## 4.5 Logical database requirements
[N/A]

## 4.6 Design constraints
[N/A]

## 4.7 Software system attributes
[N/A]

# 5 Appendices

## 5.1 Assumptions and dependencies
- There are no development assumptions or dependencies reported in the original SRS.

## 5.2 Acronyms and abbreviations
- ACM: Association for Computing Machinery
- CS: Computer Science
- ETIC: Engineering and Technology Industry Council
- FAQ: Frequently Asked Questions
- IEEE: Institute of Electrical and Electronics Engineers
- OUS: Oregon University System
- OSU: Oregon State University
- RSS: Really Simple Syndication
- SIGGRAPH: Special Interest Group on Computer GRAPHics and Interactive Techniques
- WICS: Women in Computer Science