Group Information
Member name
Percent contribution
Activities completed by the member
Karan Patel
25 %
Positioning, Stakeholders and Users, Goal Model
Karim Hemani
25 %
Introduction, Positioning, Goal Model
Rahim Dhanani
25 %
Introduction, Positioning, Goal Model
Marc Valle
25 %
Positioning, Stakeholders and Users, Product Overview
Total
100

Evaluation Summary
Section
Target %
Comments
Evaluation
Goal model
60

Positioning
10

Stakeholder
10

Introduction
10

Fit & finish
10

Total
100

Evaluation Guidelines
1. Goal model
a. Goals shall be in the form of goal pattern (achieve, avoid, cease, maintain)
b. Goals shall be structured as a tree (or hierarchy)—indicated with TOC numbering (e.g., 1, 1.1, 1.1.1) or graphically.
c. Both soft goals (non-functional, qualities) and functional goals shall be represented
d. Goals shall mainly concern the how the system meets users needs, and less about how the system is implemented (e.g., protocols, frameworks, programming languages)
2. Positioning
a. This section shall be completed according to IBM Rational guidelines. Complete all columns in the table.
3. Stakeholder
a. This section shall be completed according to IBM Rational guidelines. Complete all columns in the table.
4. Introduction
a. Use the IBM Rational template as guide. Complete sufficient information to enable an executive to understand the purpose of the document and an overview of your system.
5. Fit & finish
a. Ensure spelling, grammar, font, style, and overall look of the document is unquestionably professional.
b. Do not include IBM Rational guidance (the blue text) or sample text (e.g., the needs table in section 1.12).
c. Do not delete section headings. Leave the sections blank if so desired.
d. Place your names in section 1.4.

<Project Name>
Vision

Version <1.0>

Revision History
Date
Version
Description
Author
9/23/14
1.0
M1
Marc, Karim, Karan, Rahim

Table of Contents
1. Introduction 2
1.1 Purpose 2
1.2 Scope 2
1.3 Definitions, Acronyms, and Abbreviations 2
1.4 References 2
1.5 Analyst Certifications 2
1.6 Overview 2
2. Positioning 2
2.1 Business Opportunity 2
2.2 Problem Statement 2
2.3 Product Position Statement 2
3. Stakeholder and User Descriptions 2
3.1 Stakeholder Summary 2
3.2 User Summary [GSU.CIS:Optional] 2
3.3 User Environment [GSU.CIS:Optional] 2
3.4 Key Stakeholder or User Needs 2
4. Product Overview 2
4.1 Assumptions and Dependencies [GSU.CIS:Optional] 2
4.2 Licensing and Installation [GSU.CIS:Optional:not recommended] 2
5. Goal Model 2
5.1 <aGoal> 2
5.2 <anotherGoal> 2
Vision
1. Introduction
1.1 Purpose
The purpose of this document is to collect, document, and process needs and features of the Financial Aid System (FAS). It focuses on the needs of the students and the speed of response of financial aid. The details of how the FAS system fulfills these needs are detailed in the use-case and additional specifications.
1.2 Scope
The scope of this document is to describe the plan of the FAS system. It introduces all the stakeholders and users of FAS and presents its features. This document will give a high level view about the FAS.
1.3 Definitions, Acronyms, and Abbreviations
FAS – Financial Aid System - The Financial Aid System (FAS) is an electronic documenting and processing system of student financial aid and scholarship information. Included in this information are student demographics, credit hours, grade history, 1084-T form, parent’s financial history.
UI – user interface
UML – Unified Modeling Language
Free Application for Federal Student Aid (FAFSA) – FAFSA is a form that can be prepared annually by current and prospective college students (undergraduate and graduate) in the United States to determine their eligibility for student financial aid (including the Pell Grant, Federal student loans and Federal Work-Study).
CSR – Computerized Student Records
References
[1] http://en.wikipedia.org/wiki/FAFSA

1.4 Analyst Certifications
We, Karim Hemani, Marc Valle, Karan Patel,