oraserv.cs.siena.eduoraserv.cs.siena.edu/.../requirements_specificationupdated.docx · web...

Requirements Specification

Networking for Antique Truck Owners (N.A.T.O.)

Requested by:

Dr. Timoth LedermanProfessor

Department of Computer ScienceSiena College

Delivered By:

Infinite Solutions

Prepared By:

Robert DeSarboTimothy Egan

Alexander EvanciewAlexander Johnson

Kelly MonroeDavid Nopper

November 4, 2009

Table of ContentsN.A.T.O.

1.1 Product Overview and Summary......................................................................................................3

1.2 Development, Operating, and Maintenance Environments..................................................3

1.3 User Case Narrative................................................................................................................................ 4

1.4 UML Use Case Diagram......................................................................................................................... 6

1.4.1 UML Use Case Key...............................................................................................................................6

1.4.2 UML Use Case Diagram.....................................................................................................................7

1.5 Data Flow Diagrams............................................................................................................................... 8

1.5.1 Data Flow Diagram Key....................................................................................................................8

1.5.2 Context Diagram.................................................................................................................................. 9

1.5.3 Level 0 Diagram................................................................................................................................ 10

1.5.4 Level 1 Process 2: Manage Accounts.......................................................................................11

1.5.5 Level 1 Process 3: Manage Directions.....................................................................................12

1.6 Functional Requirements Inventory............................................................................................13

1.6.1 General User Interface Functional Requirements..............................................................13

1.6.2 Member Functional Requirements...........................................................................................13

1.6.3 Administrator Functional Requirements...............................................................................16

1.6.4 Super Administrator Functional Requirements.................................................................20

1.7 Non Functional Requirements Inventory..................................................................................24

1.8 Exception Handling.............................................................................................................................. 25

1.9 Early Subsets and Implementation Priorities..........................................................................25

1.10 Foreseeable Modifications and Enhancements.......................................................................25

1.11 Testing Requirements and Acceptance Criteria......................................................................26

1.12 Design Hints and Guidelines............................................................................................................26

1.13 Appendencies......................................................................................................................................... 27

1.13.1 Timeline-Gantt Chart...................................................................................................................... 28

1.13.2 Glossary of Terms.............................................................................................................................29

Infinite Solutions Networking for Antique Truck Owners (N.A.T.O.) 2Requirements Specification

1.1 Product Overview and Summary (Top)

Client Dr. Timoth Lederman presented Infinite Solutions with the task of improving the current MapBuilder mashup of the OldGMCtrucks.com website users. The Networking for Antique Truck Owners (N.A.T.O.) project will result in the creation of the software product, also referred to as Networking for Antique Truck Owners (N.A.T.O.). The main purpose of the MapBuilder mashup is to allow OldGMCtrucks.com website users the ability to locate other members by a map. N.A.T.O. will adopt this purpose, but also improve upon the functionality by means of increased user capabilities and interface ease of use. N.A.T.O. will be utilized by three main user types: Member, Administrator, and Super Administrator. The most significant functions of N.A.T.O. will be the Member ability to add, edit, and delete Member personal information and map pin location, ability of all user types to obtain directions between map locations, and the ability to generate printable reports from user based searches. The Super Administrator will share the same functions as Administrator, to monitor and modify all accounts and content, with the exception that client Dr. Timoth Lederman will be the sole Super Administrator, which will not be able to be deleted.

1.2 Development, Operating, and Maintenance Environments (Top)

The development, operation, and maintenance of N.A.T.O. will be conducted in Roger Bacon Hall room 348, the Software Engineering Lab, on an Oracle web server. All development, operation, and maintenance of N.A.T.O. will be conducted by means of two computer terminals, the first being a Dell Optiplex 760 equipped with an Intel Core Duo 2.93 GHz processor and 4 GB of ram. The Operating System that the Dell Optiplex 760 is running is Windows Vista Service Pack 2. The second computer terminal is an Apple I-Mac built with an Intel Core Duo 2 GHz processor and 1 GB of RAM. The Operating System of the Apple I-Mac is OS X version 10.4.11. The Dell Optiplex 760 will be the main environment in the development, operation, and maintenance of N.A.T.O. The Dell Optiplex 760 is equipped with software installations of Microsoft Office 2007, version 11.5.3, and Adobe Creative Suite 2004, version 7.0.1. N.A.T.O. will be tested and compatible with Microsoft Internet Explorer, Mozilla Firefox, and Apple Safari. Access to N.A.T.O. will be available on any computer running any of the preceding browsers.


1.3 User Case Narrative (Top)

Member

The Member will have the ability to login and logout of the application by means of a unique username and password. Once logged in, the Member will be able to view and utilize the Member Tools menu. The Member will also be able to view and interact with the map. The Member’s personal information will be presented on the site, therefore the Member will have the ability to add, edit, delete or hide the Member’s personal information. In similar fashion to the Member’s personal information, the Member will have the ability to add, edit, delete or hide the Member’s personal pin on the map. If the Member no longer desires affiliation with the map, the Member will have the ability to delete the Member’s account. Due to constraints on the Member, the Member must request that the Member’s username or email address be changed by the Administrator. The Member will have the ability to create an event, and to modify and delete any event which the Member has created. The Member will have the ability to generate search reports. Finally, the Member will have the ability to request directions between two locations.

Administrator

The Administrator will have the ability to login and logout of the application by use of a unique username and password. Once logged in, the Administrator will have the ability to switch between a standard Member mode and an Administrator mode, while utilizing the Administrator and Member Tools menus. The Administrator will have the ability to view and interact with the map. The Administrator will have the ability to add, edit, delete or hide the Administrator’s personal information, the Member’s personal information, as well as other Administrators’ personal information. In accordance with personal information, the Administrator will have the ability to add, edit, delete or hide the Administrator’s personal pin, in addition to the Member’s pin and other Administrators’ pins. Upon a Member’s request for account creation, the Administrator will be notified by an email, and the Administrator will have the ability to approve the creation of a new account. The Administrator will be notified when a new account is created. The Administrator will be notified when a Member requests to have the Member’s username or email address changed, and the Administrator will have the ability to approve and perform a Member’s request to change the Member’s username or email address. The Administrator will have the ability to create a new Administrator account. The Administrator will be notified when a new Administrator account is created. The Administrator will have the ability to delete the Administrator’s account, the account of another Administrator, and the Member’s account. The Administrator will be notified when an Administrator account is deleted. The


Administrator will have the ability to create an event, and to modify and delete any event created. The Administrator will have the ability to generate search reports. Finally, the Administrator will have the ability to request directions between two locations.

Super Administrator

The Super Administrator will be a sole entity with the inability to be deleted. The Super Administrator will have the ability to login and logout of the application by use of a unique username and password. Once logged in, the Super Administrator will have the ability to switch between a standard Member mode and a Super Administrator mode, and utilize Super Administrator and Member Tool menus. The Super Administrator will have the ability to view and interact with the map. The Super Administrator will have the ability to add, edit, delete or hide the Super Administrator’s personal information, the Administrator’s personal information, and the personal information of the Member. In similar fashion to personal information, the Super Administrator will have the ability to add, edit, delete or hide the Super Administrator’s personal pin, the Administrator’s pin, and the pin of the Member. Upon a Member request for account creation, the Super Administrator will be notified and the Super Administrator will have the ability to approve the creation of the new User. The Super Administrator will also be able to create an Administrator, and the Super Administrator will be notified when a Member or Administrator are created. The Super Administrator will be notified when a Member or Administrator requests to have the User’s or Administrator’s username or email address changed. The Super Administrator will have the ability to approve the Member’s or Administrator’s request to have the Member’s or Administrator’s username or email address changed. The Super Administrator will have the ability to delete a Member and the Administrator. The Super Administrator will be notified when the Administrator is deleted. The Super Administrator will have the ability to create an event. The Super Administrator will have the ability to modify and delete any event created. The Super Administrator will have the ability to generate search reports. Finally, the Super Administrator will have the ability to request directions between two locations.


1.4 UML Use Case Diagram (Top)

The purpose of the UML Use Case Diagram is to depict the general functionality and users of a system. Four main elements compose the diagram: the Actor, Use Case, System, and Relationship. The System is N.A.T.O. The Actor includes any human or non human user of N.A.T.O., thus the Member, Administrator, Super Administrator, Web server, Database Management System, Google Maps, and possible Applets. The Use Case is a scenario or action that an Actor has the ability to perform within the System. The Use Cases for N.A.T.O. are Validate, View, Edit, Delete, and Search. A Relationship is the representation of the interaction between the Actor and System.

1.4.1 UML Use Case Key (Top)

See Section 1.4 UML Use Case Diagram for a description of the following:


1.4.2 UML Use Case Diagram (Top)


1.5 Data Flow Diagrams (Top)

A Data Flow Diagram (DFD) is pictorial representations of the transfer and transformation of data within a system at various levels of detail. The four main elements of the diagrams are External Entities, Processes, Data Stores, and Data Flows. The most general diagram is a Context Diagram, which simply shows the human users of the system as External Entities. The Level 0 Diagram depicts the Data Flows between External Entities, the general system Processes, or functions, and the Data Store, which is the database. Each Process of the Level 0 Diagram is numbered; these numbers act as the next Level of Diagram. The Level 2 and 3 Diagrams break down their corresponding Process into more detailed Processes and Data Flows.

1.5.1 Data Flow Diagram Key (Top)

External Entities are either sources or recipients that contribute or receive data or information to the system. The Entities either supply or terminate data flow. A Process transforms or directs data flows; the Process’ name is the action that the Process performs. Data Stores represent locations that simply hold data temporarily or permanently. The final object is a Data Flow. The Data Flow arrow symbolizes data flowing to or from a Process, External Entity, or Data Store. A Data Flow must originate or end at a Process and be named in accordance with the data it is carrying.


1.5.2 Context Diagram (Top)

This is the highest level and represents the overall system (N.A.T.O.) and its interaction with its External Entities, in our case the Users of our system.


1.5.3 Level 0 Diagram (Top)

This level shows the major Processes of N.A.T.O. and their interactions with N.A.T.O.’s Users.


1.5.4 Level 1 Process 2: Manage Accounts (Top)

Takes a specific major Process and breaks down its Processes and Data Flows.


1.5.5 Level 1 Process 3: Manage Directions (Top)


1.6 Functional Requirements Inventory (Top)

Functional Requirements Inventory is a complete, detailed list of all system functions agreed upon by the client and the development team. The Functional Requirements Inventory is outlined by General User Interface, Member, Administrator, and Super Administrator.

1.6.1 General User Interface Functional Requirements (Top)

Will have two separate colors for pins: Member, Administrator, and Super Administrator location and event location

Will have the ability to search the map for Member’s, Administrator’s, Super Administrator’s username and last name

Will have the ability to upload and edit pictures Will have the ability to generate directions between two points Will have the ability to undo changes

1.6.2 Member Functional Requirements (Top)

Will have the ability to access the site through secure authentication Will have the ability to request forgotten password Will have the ability to login Will have the ability to logout Will have the ability to view the Member tools menu Will have the ability to use the Member tools menu Will have the ability to view the map Will have the ability to interact with the map Will have the ability to zoom in on the map Will have the ability to zoom out on the map Will have the ability to pan the map Will have the ability to add personal information

o Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box


Member Functional Requirements, Continued (Top)

Will have the ability to edit personal informationo Update First Nameo Update Last Nameo Update Address o Update Geo-locationo Update Pictures o Shoutout Box

Will have the ability to delete personal informationo Update First Nameo Update Last Nameo Update Address o Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to add self pin to map Will have the ability to edit self pin on the map Will have the ability to delete self pin on the map Will have the ability to delete account Will have the ability to change password Will have the ability to request an email change from an Administrator Will have the ability to view and event

o View list of attendees and guestso View Timeo View Address of Location o View Date o View Contact Persono View Name of Hosting Organizationo View Organization’s Web Page Linko View Registration Page/Document Link (If available)o View Informational Flyer Link (If available)o View Event Nameo View Descriptiono View Geo-locationo View Addresso Get directions from User location to event location


Member Functional Requirements, Continued (Top)

Will have the ability to create an evento Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Nameo Update Descriptiono Update Geo-locationo Update Address

Will have the ability to modify a self evento Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Nameo Update Descriptiono Update Geo-locationo Update Address

Will have the ability to register for an evento Update List of Guestso Update Means of Transportation

Will have the ability to cancel registration for an event Will have the ability to delete a self event Will have the ability to generate search reports

o Update Print reporto Update Be able to search by usernameo Update Be able to search by last name

Will have the ability to request directions between two locations


o Update From their location to another locationo Update From another location to their location

1.6.3 Administrator Functional Requirements (Top)

Will have the ability to access the site through secure authentication Will have the ability to request forgotten password Will have the ability to login Will have the ability to logout Will have the ability to view the Member tools menu Will have the ability to use the Member tools menu Will have the ability to view the Administrator tools menu Will have the ability to use the Administrator tools menu Will have the ability to switch between Member and Administrator views Will have the ability to view the map Will have the ability to interact with the map Will have the ability to zoom in on the map Will have the ability to zoom out on the map Will have the ability to pan the map Will have the ability to add personal information


Will have the ability to edit personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to delete personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box


Administrator Functional Requirements, Continued (Top)

Will have the ability to add Member personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to edit Member personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to delete Member personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to add Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to edit Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures


o Update Shoutout Box


Will have the ability to delete Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to add self pin to map Will have the ability to edit self pin on the map Will have the ability to delete self pin on the map Will have the ability to add pin of Member on map Will have the ability to edit pin of Member on map Will have the ability to delete pin of Member on map Will have the ability to add pin of Administrator on map Will have the ability to edit pin of Administrator on map Will have the ability to delete pin of Administrator on map Will have the ability to create Member account Will have the ability to delete Member account Will have the ability to create Administrator account Will have the ability to delete Administrator account Will have the ability to delete self account Will have the ability to change password Will have the ability to request an email change from an Administrator Will have the ability to approve Member email request change Will have the ability to view and event

o View list of attendees and guestso View Timeo View Address of Location o View Date o View Contact Persono View Name of Hosting Organizationo View Organization’s Web Page Linko View Registration Page/Document Link (If available)


o View Informational Flyer Link (If available)


o View Event Nameo View Descriptiono View Geo-locationo View Addresso Get directions from User location to event location

Will have the ability to create an evento Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Nameo Update Descriptiono Update Geo-locationo Update Address

Will have the ability to modify any evento Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Nameo Update Descriptiono Update Geo-location


o Update Address Will have the ability to register for an event

o List of Guestso Means of Transportation

Will have the ability to cancel registration for an event Will have the ability to delete any event

Will have the ability to generate search reportso Print reporto Be able to search by usernameo Be able to search by last name

Will have the ability to request directions between two locationso From their location to another locationo From another location to their location

1.6.4 Super Administrator Functional Requirements (Top)

Will have the ability to access the site through secure authentication Will have the ability to request forgotten password Will have the ability to login Will have the ability to logout Will have the ability to view the Member tools menu Will have the ability to use the Member tools menu Will have the ability to view the Administrator tools menu Will have the ability to use the Administrator tools menu Will have the ability to switch between Member and Administrator views Will have the ability to view the map Will have the ability to interact with the map Will have the ability to zoom in on the map Will have the ability to zoom out on the map Will have the ability to pan the map Will have the ability to add personal information

o Update First Nameo Update Last Nameo Update Addresso Update Geo-location


o Update Pictures o Update Shoutout Box

Super Administrator Functional Requirements, Continued (Top)

Will have the ability to edit personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to delete personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to add Member personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to edit Member personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to delete Member personal information




Will have the ability to add Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to edit Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to delete Administrator personal informationo Update First Nameo Update Last Nameo Update Addresso Update Geo-locationo Update Pictures o Update Shoutout Box

Will have the ability to add self pin to map Will have the ability to edit self pin on the map Will have the ability to delete self pin on the map Will have the ability to add pin of Member on map Will have the ability to edit pin of Member on map Will have the ability to delete pin of Member on map Will have the ability to add pin of Administrator on map


Will have the ability to edit pin of Administrator on map Will have the ability to delete pin of Administrator on map Will have the ability to create Member account Will have the ability to delete Member account Will have the ability to create Administrator account Will have the ability to delete Administrator account Will have the ability to change password Will have the ability to request an email change from an Administrator Will have the ability to approve Member email request change


Will have the ability to view and evento View list of attendees and guestso View Timeo View Address of Location o View Date o View Contact Persono View Name of Hosting Organizationo View Organization’s Web Page Linko View Registration Page/Document Link (If available)o View Informational Flyer Link (If available)o View Event Nameo View Descriptiono View Geo-locationo View Addresso Get directions from User location to event location

Will have the ability to create an evento Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Nameo Update Descriptiono Update Geo-location


o Update Address Will have the ability to modify any event

o Update Timeo Update Address of Location o Update Date o Update Contact Persono Update Name of Hosting Organizationo Update Organization’s Web Page Linko Update Registration Page/Document Link (If available)o Update Informational Flyer Link (If available)o Update Event Name


o Update Descriptiono Update Geo-locationo Update Address

Will have the ability to register for an evento List of Guestso Means of Transportation

Will have the ability to cancel registration for an event Will have the ability to delete any event Will have the ability to generate search reports

o Print reporto Be able to search by usernameo Be able to search by last name

Will have the ability to request directions between two locationso From their location to another locationo From another location to their location

1.7 Non Functional Requirements Inventory (Top)

As a user driven product, N.A.T.O. must appeal to its users in a variety of non-functional ways. Such ways include user interface, aesthetics, and more but are difficult to test because they are unquantifiable. These requirements explain how N.A.T.O. is supposed to be not what it does. As such; N.A.T.O. will be a cross platform compatible, multi-browser capable, web based mapping utility. The use of N.A.T.O. will result in the same experience


on Windows Vista and Apple OSX, as well as on Microsoft Internet Explorer, Mozilla Firefox or Apple Safari web browsers. All data entered into the N.A.T.O database will be confidential and used only for the purposes of the system. All data entered into the N.A.T.O database will be a permanent part of the data records; no data can be physically removed. N.A.T.O will be robust and have proficient exception handling. The user interface of N.A.T.O. will be intuitive and user-friendly. N.A.T.O will have the ability to migrate to any compatible web server. Other non-functional requirement may be later discovered and added through future client meetings.

1.8 Exception Handling (Top)

As the status of the project advances through the design phase, exceptions or special cases, which would interrupt the normal flow of N.A.T.O., will be identified and handled accordingly. The discovery process of exceptions or special cases will be conducted by use of code walkthroughs and thorough software testing to identify when, why, and how the exceptions or special cases are triggered. Once identified, subroutines will be created to catch exceptions or special cases and return N.A.T.O. to the non exception state.

1.9 Early Subsets and Implementation Priorities (Top)

The critical components of N.A.T.O. are as follows: Member, Administrator, and Super Administrator ability to view, add, edit and

delete profile information Member, Administrator, and Super Administrator ability to view, add, edit, and

delete pins on the map Member, Administrator, and Super Administrator ability to search for Member,

Administrator, and Super Administrator locations and events on the map Administrator and Super Administrator ability delete other pins, profile information

and accounts Super Administrator will have the inability to be deleted

1.10 Foreseeable Modifications and Enhancements (Top)

Beyond the scope of the project, the following are possible modifications or enhancements: Display list of all currently logged in Members, Administrators, Super Administrator


Daemon process to log out inactive Members, Administrators, Super Administrator after a certain period of time

Administrator ability to change banner section of the website, or place a logo Hover over the pin for the username (minimum) Fix dialog box so that the map centers and zooms on a Member’s, Administrator’s,

Super Administrator’s pin when viewing Offer precision placement of pin when Member, Administrator, Super Administrator

initially set up to correct possible misplacement by Google Maps At least nine possible pin colors Ability to search by additional criteria

1.11 Testing Requirements and Acceptance Criteria (Top)

At this stage of N.A.T.O’s development, the Testing Requirements and Acceptance Criteria have not been finalized. As the status of the project progresses through the Preliminary Design and Detailed Design phases a more complete version will be created. The Testing Requirements will include all Functional Requirements and Non-Functional Requirements that are listed in Section 1.6. The Functional Requirements will be the priority of the testing. The Non-Functional Requirements are non-quantifiable, and therefore difficult to test accurately. The final Testing Requirements and Acceptance Criteria will also be comprised of all unit level testing, as well as a complete system test to ensure that all unit functions interact sufficiently.

1.12 Design Hints and Guidelines (Top)

During the Preliminary Design and Detailed Design phases, the following guidelines will be followed:

N.A.T.O. will utilize minimal pop-ups N.A.T.O. will utilize Google Applications, including Google Maps The home screen of N.A.T.O. will have the map as the dominant feature N.A.T.O will have an expandable side toolbar All information entered into the N.A.T.O. database will be retained N.A.T.O. will utilize an applet to find geo-location


1.13 Appendices (Top)

The Appendices for this document are the Timeline which is in the form of a Gantt Chart, and the Glossary of Terms.


1.13.1 Time Line- Gantt Chart (Top)


1.13.2 Glossary of Terms (Top)

Actor – component of UML Use Case Diagram which represents any human or non-human entity that interacts with the System

Database – A structured collection of records or data stored on a computer system.

Data Flow Diagram – (DFD) a pictorial representation of the flow of data in a Software System which is comprised of varying levels of detail

Data Flows – component of DFD that represents the movement of data from an External Entity to a Process or Data Store, and vice versa

Data Stores – a component of DFD that represents any location in which information or data is held, the most common being a database

DFD – see Data Flow Diagram

External Entities – component of DFD that represents any human or non-human user of a Software System

Functional Requirements – measurable actions that the system must be able to execute

Geo-Location – the longitude and latitude position of a point

Mashup – A web page or application that combines data or functionality from two or more external sources to create a new source.

Non-Functional Requirements – specifies how a product is supposed to be, compared to functional requirements that describe what the product does. Such examples are the user interface, aesthetics, accessibility, maintainability, security, etc. Non-functional are difficult, if not impossible to quantifiably test.

Pin – “map marker” that depicts a location of a user or event on a map

Processes – component of DFD that represents any scenario or action within a Software System

Relationship – component of UML Use Case Diagram which represents the interactions between the Actor and the System

Shoutout Box – a dialog box granting the user the ability to enter personal information

System – component of UML Use Case Diagram which represents the Software System


UML (Unified Modeling Language) Use Case Diagram – A general pictorial explanation of the basic processes of a Software System used by Software Development Teams

Use Case – component of UML Use Case Diagram which represents any process located within the System and performable by an Actor

User Case Narrative – a textual explanation of the functions and abilities users for a Software System


oraserv.cs.siena.eduoraserv.cs.siena.edu/.../requirements_specificationupdated.docx · web...

Documents