# 1 Introduction
[NULL]

## 1.1 Purpose
The purpose of the software described in this document is to update the http://getreal.ous.edu website and its associated support pages. The Get Real website aims to attract and encourage Oregon high school students to pursue coursework leading to a baccalaureate degree in computer science at one of the seven Oregon University System campuses. This document outlines the requirements for the second revision of the website, with the potential for future updates.

## 1.2 Scope
The software product under consideration is the "Get Real" website, specifically version 2, which is an update of the existing website initially created in 2006. The primary objective of the Get Real website is to attract and encourage Oregon high school students to pursue coursework leading to a baccalaureate degree in computer science (CS) at one of the seven Oregon University System campuses.

The website aims to provide a teen-friendly set of web pages that are easy to navigate while offering comprehensive information about careers in computer science. It targets two main groups of students: those already interested in CS seeking more in-depth information and college-bound students who might be persuaded to consider a CS career with the right information.

The goals of the Get Real website include increasing the number of computer science graduates from Oregon universities by encouraging more students to choose computer science and related majors. The site will offer benefits such as personal and career information from a broad spectrum of CS professionals, CS course information from OUS campuses, timely updates, and actionable plans for students to prepare for a CS career. Maintaining a teen-friendly design is crucial to engage students and guide them toward pursuing a career in CS.

## 1.3 Product overview
[NULL]

### 1.3.1 Product perspective
The Get Real website is an update of the existing Get Real web site version 1, transitioning to version 2. It operates as an extension of the Oregon University System (OUS) site, specifically under the domain ~getreal.ous.edu~, which maximizes visibility through search engines like Google. The site is hosted on OSU servers.

#### System interfaces
The Get Real site is integrated within the OUS domain, which enhances its search engine optimization. There are no specific system interfaces detailed in the original document.

#### User interfaces
The website should be compatible and tested with major web browsers such as Internet Explorer, Firefox, and Netscape. The design should be teen-friendly, with a focus on easy navigation, visually appealing graphics, and interactive elements to engage high school students.

#### Hardware interfaces
There are no special hardware interface requirements specified for the Get Real website.

#### Software interfaces
The website development utilizes Dreamweaver, adhering to CSS and style conventions established in version 1. There are no additional software interface requirements specified.

#### Communications interfaces
There are no special communication interface requirements specified for the Get Real website.

#### Memory constraints
[N/A]

#### Operations
The website should provide rapid response times to accommodate the short attention spans of high school students. It should be capable of handling both interactive and unattended operations, with a focus on user-initiated interactions.

#### Site adaptation requirements
[N/A]

#### Interfaces with services
[N/A]

### 1.3.2 Product functions
The Get Real website is designed to attract and encourage Oregon high school students to pursue a career in computer science. The major functions of the website include:

- **Exploring College**: Provides information on computer science offerings from Oregon University System campuses and other Oregon colleges.
- **Jobs & Money**: Answers questions about societal contributions and potential earnings with a computer science degree.
- **Real People**: Features profiles of recent CS graduates and experienced professionals, showcasing diverse career paths.
- **Women in Computing**: Profiles women in computer science and engineering, highlighting their contributions and community involvement.
- **Resources**: Offers a range of pre-college technology programs and courses for high school students.
- **I’m Looking For...**: A Q&A section with links to topics such as money, people, and colleges.
- **Articles**: Lists external articles related to careers in computer science.
- **High School Courses**: Recommends curricula for high school students interested in CS and related careers.
- **Search for Additional Information**: Provides internal and external search capabilities for CS-related content.
- **Professional Organizations**: Lists and links to major CS organizations like ACM and IEEE.
- **RSS Feeds**: Delivers current CS information through RSS subscriptions.
- **Ask a Grad or Prof – FAQ**: Offers a Q&A format for quick feedback from the Oregon University System.
- **Consider a CS Minor**: Provides information on the value of a CS minor for students in various professions.

These functions are designed to create a teen-friendly, informative, and engaging platform that encourages students to explore and pursue careers in computer science.

### 1.3.3 User characteristics
The primary users of the Get Real website are Oregon high school students, specifically those in grades 9 to 12 across all high schools in Oregon. These students can be categorized into two main groups:

1. **Students interested in Computer Science (CS):** These users are seeking more detailed information about a career in CS. They are likely to have a higher level of interest and possibly some foundational knowledge in the field.

2. **College-bound students not initially interested in CS:** This group may not have a pre-existing interest in CS but could be persuaded to consider a CS career with the right information and encouragement from the website.

A potential third group includes students interested in diverse fields such as protein research, weather prediction, neurobotics, medicine, law, or other sciences, where a CS minor could enhance their understanding of data and information.

Feedback from Oregon high school students indicates a need for a website that is visually appealing and easy to navigate, with a preference for more interactive and engaging content. Students not generally interested in CS have expressed a desire for more white space, pictures, and a layout that breaks information into digestible chunks, avoiding "walls of text." They also appreciate visual elements like color, photos, diagrams, and charts to make the site more attractive.

Students interested in CS and engineering have suggested improvements in sections like Real People, Resources, and Colleges, emphasizing the importance of visual content and concise information. Overall, the website should cater to a range of technical expertise and educational levels, ensuring accessibility and engagement for all user groups.

### 1.3.4 Limitations
- **Hardware Limitations**: The website must operate within the constraints of space and bandwidth, particularly for video streaming.
- **Interfaces to Other Applications**: The site is an extension of the OUS site and must integrate seamlessly with it to maximize search engine hits.
- **Quality Requirements**: The site must provide adequate response time to accommodate the short attention spans of high school students.
- **Security Considerations**: Copyright and security measures should align with those of the OUS site.
- **Design Constraints**: Limited availability of resources from the Chancellor’s Office may impact the design and implementation of the website.
- **Criticality of the Application**: The site is critical in encouraging Oregon high school students to pursue computer science careers, thus requiring a high level of usability and engagement.
- **Safety and Security Considerations**: The site must adhere to the security standards of the OUS domain to ensure data protection and user privacy.
- **Physical/Mental Considerations**: The design should be teen-friendly, with a focus on visual appeal and ease of navigation to maintain user engagement. 

[N/A] for any other limitations not explicitly mentioned in the original SRS.

## 1.4 Definitions
[N/A]

# 2 References
## Compliance
- [N/A]

## Guidance
- For web page development at the Capital Center, use the local site files for Dreamweaver on `~cn-capctr/share/Get_Real_website/~`. Be cautious of others modifying pages on the site. Always use Dreamweaver check in/out feature. Adhere to CSS and other style conventions established in Get Real version 1.
- Example video "real people" profiles: Computer science students and young professionals are presented here: "a day in the life of," "power to change the world," and "Pathways in computer science" at http://www.cs.washington.edu/education/ugrad/prospective/download.html. Reviewers of this document should review these videos – click the link above then "Video Downloads Available."
- Women in Computer Science resources: WICS UO, www.cs.uoregon.edu/groups/wics/ and www.cis.upenn.edu/acg/wicarch.html. This site lists a resource for those wishing to contact women in computer architecture. Get Real might use a similar list for girls interested in contacting recent grads or women CS professionals.

# 3 Requirements
[NULL]

## 3.1 Functions
The Get Real website is designed to attract and encourage Oregon high school students to pursue a career in computer science. The fundamental actions of the website include:

- **Input Processing and Validity Checks**: The website will accept user inputs such as search queries and navigation selections. Validity checks will ensure that inputs are within expected parameters, such as valid search terms and navigation paths.

- **Sequence of Operations**: The website will guide users through a series of pages and sections, including "Exploring College," "Jobs & Money," "Real People," and "Women in Computing." New sections like "High School Courses" and "Professional Organizations" will be prototyped and prioritized.

- **Responses to Abnormal Situations**:
  - **Overflow**: The website will handle data overflow by limiting the number of search results displayed at one time and providing pagination.
  - **Communication Facilities**: The website will ensure stable communication with the server, providing error messages if connectivity is lost.
  - **Hardware Faults and Failures**: The website will be hosted on reliable servers to minimize downtime and will display maintenance messages during server outages.
  - **Error Handling and Recovery**: The website will provide user-friendly error messages and options to retry actions or return to the homepage in case of errors.

- **Effect of Parameters**: User preferences, such as selected topics or search filters, will affect the content displayed, allowing for a personalized experience.

- **Relationship of Outputs to Inputs**:
  - **Input/Output Sequences**: User inputs, such as search terms, will generate corresponding outputs, like search results or navigational paths.
  - **Formulas for Input to Output Conversion**: The website will use algorithms to match user queries with relevant content, ensuring accurate and useful results.

The website's functional requirements are designed to provide a seamless and engaging experience for high school students, encouraging them to explore computer science as a viable career path.

## 3.2 Performance requirements
The Get Real site should be hosted on a server that can provide adequate response time to ensure a satisfactory user experience for high school students, who tend to have short attention spans. The current OUS (www.ous.edu) site serves as a benchmark for rapid response time. Specific numerical performance requirements, such as the number of simultaneous users supported or the amount of data processed within certain time periods, are not detailed in the original document. [N/A]

## 3.3 Usability requirements
The Get Real website must be designed to be teen-friendly, ensuring ease of navigation and engagement for high school students. The site should incorporate visually appealing elements such as color, photos, diagrams, and charts to break up text and maintain user interest. The design should avoid "walls of text" and instead present information in concise, readable chunks, using bullets and charts where possible to accommodate shorter attention spans.

Feedback from Oregon high school students indicated a preference for more white space, pictures, and easier navigation. The site should "speak to them" and offer value even to those not initially interested in computer science. The inclusion of interactive elements, such as a spinning globe and satellite menu, received positive feedback and should be considered in the design.

The website should also provide a rapid response time to accommodate the short attention spans of high school students, ensuring that the server hosting the site can deliver adequate performance. The current OUS site serves as a benchmark for the desired response time.

Overall, the usability requirements focus on creating an engaging, accessible, and visually appealing experience that encourages students to explore careers in computer science.

## 3.5 Logical database requirements
[N/A]

## 3.6 Design constraints
The design of the Get Real website is subject to several constraints:

- **Space and Bandwidth**: The website must operate within the limitations of available space and bandwidth, particularly for video streaming.
- **Resource Availability**: There is limited availability of resources from the Chancellor’s Office, which may impact the design and implementation process.
- **Web Design Conventions**: The website must adhere to CSS and other style conventions established in Get Real version 1, ensuring consistency with the standards and conventions used on the OUS site.
- **Browser Compatibility**: The site should be compatible with and tested against Internet Explorer, Firefox, and Netscape to ensure accessibility for all users.
- **Server Performance**: The site should be hosted on a server that can provide adequate response time, as high school students tend to have short attention spans, and a slow server would not be satisfactory for this application.
- **Security Measures**: Copyright and other security measures for Get Real should align with those of the OUS site to ensure data protection and compliance with existing standards. 

These constraints must be considered during the design phase to ensure the successful implementation and operation of the Get Real website.

## 3.7 Software system attributes
### a) Reliability
[N/A]

### b) Availability
The Get Real site should be hosted on a server that can provide adequate response time. High school students tend to have short attention spans, so a slow server would not be satisfactory for this application. The current OUS (www.ous.edu) site is a good example of rapid response time.

### c) Security
Copyright and other security measures for Get Real should be the same as the OUS site.

### d) Maintainability
Web design conventions should be consistent with the standards and conventions used on the OUS site.

### e) Portability
[N/A]

## 3.8 Supporting information
a) Sample input/output formats, descriptions of cost analysis studies, or results of user surveys are not explicitly provided in this document. However, feedback from Oregon high school students was gathered to inform design changes, emphasizing the need for a more visually appealing and navigable site.

b) Supporting or background information includes the need to attract and encourage Oregon high school students to pursue computer science degrees, as well as the importance of maintaining a teen-friendly site to hold student attention.

c) The primary problem to be solved by the software is to increase the number of computer science graduates from Oregon universities by providing engaging and informative content that encourages high school students to consider careers in computer science.

d) There are no special packaging instructions for the code and media mentioned in this document.

The SRS does not explicitly state whether these information items are to be considered part of the requirements. [N/A]

# 4 Verification
[NULL]

## 4.1 Functions
[N/A]

## 4.2 Performance requirements
The verification of performance requirements for the Get Real website will focus on ensuring that the site is hosted on a server capable of providing adequate response times. This is crucial as high school students, the primary users, tend to have short attention spans, and a slow server would not be satisfactory. The current OUS site serves as a benchmark for rapid response time.

Verification methods will include:

- **Load Testing**: Simulate multiple users accessing the site simultaneously to ensure the server can handle peak loads without degradation in performance.
- **Response Time Measurement**: Measure the time taken for pages to load under various conditions to ensure they meet the required performance standards.
- **Capacity Testing**: Verify the number of simultaneous users the site can support without performance issues.

The performance requirements will be considered met if:

- 95% of the page requests are processed in less than 1 second under normal load conditions.
- The site can support a specified number of simultaneous users without significant performance degradation.

These tests will ensure that the site remains responsive and user-friendly, maintaining the interest of high school students.

## 4.3 Usability requirements
The usability requirements for the Get Real website focus on creating a high school teen-friendly interface that is easy to navigate and visually appealing. The site should maintain a design that holds student attention and guides them to information that encourages pursuing a career in computer science. Key usability objectives include:

- **Effectiveness**: The website should effectively provide information about careers in computer science, including personal and career information from a broad spectrum of CS professionals, CS course information from OUS campuses, and timely updates that encourage return visits.

- **Efficiency**: The site should allow users to quickly find and access the information they need. This includes implementing design changes to existing pages to shorten paragraphs, add bullet points, and incorporate charts for faster reading.

- **Satisfaction**: The site should be visually attractive, incorporating color, photos, diagrams, and charts to break up text and make the site appealing. Feedback from students indicated a preference for more white space, pictures, and easier navigation.

- **Avoidance of Harm**: The site should avoid overwhelming users with "walls of text" and instead present information in manageable, engaging chunks. The design should cater to both students interested in CS and those who might be attracted to the field with the right information.

Verification of these usability requirements will involve user testing with high school students to ensure the site meets their needs and preferences. Feedback will be gathered to make iterative improvements to the design and content presentation.

## 4.5 Logical database requirements
[N/A]

## 4.6 Design constraints
[N/A]

## 4.7 Software system attributes
[N/A]

# 5 Appendices
[NULL]

## 5.1 Assumptions and dependencies
[N/A]

## 5.2 Acronyms and abbreviations
[N/A]
