| |
Software Features |
| |
|
|
|
| |
Infrastructure |
 |
Track hardware and software specifications
|
| |
|
|
Identify needed databases, server
applications, and development tools |
| |
|
|
|
| |
Premise |
|
Start the project off on the right
foot by defining an affective business case, vision, and scope |
| |
|
|
|
| |
Risks |
|
Identify potential trouble spots
in the project |
| |
|
|
Assign risks to team members and
track their mitigation of risks |
| |
|
|
|
| |
Team |
|
Identify the customers and consultants
who will participate in the project |
| |
|
|
|
| |
Ideas |
|
Collect and verify unstructured customer
input |
| |
|
|
Review and revise ideas |
| |
|
|
Flag ideas as requirements |
| |
|
|
Link ideas and requirements to their
relevant design components |
| |
|
|
|
| |
Actors |
|
Identify roles that will be assumed
by system users |
| |
|
|
Manage group level access |
| |
|
|
|
| |
Use Cases |
|
Use "Use Cases" as a component
of Unified Modeling Language |
| |
|
|
Describe functions that will be performed
within the system |
| |
|
|
Determine CRUD rules for each Object
Attribute |
| |
|
|
Identify Screens that will implement
the Use Case |
| |
|
|
|
| |
System Requirements |
|
Identify requirements that will be
implemented system wide |
| |
|
|
|
| |
Glossary |
|
Define terms that have a specific
meaning within the context of the project |
| |
|
|
|
| |
Screens |
|
View and manage prototype screens |
| |
|
|
Determine the CRUD rules for each
object attribute |
| |
|
|
Identify use cases to be implemented |
| |
|
|
|
| |
Reports |
|
Design system reports |
| |
|
|
Display a mock-up of the report as
any Microsoft Office document |
| |
|
|
Identifies the data that will be
included in the report along with sort criteria |
| |
|
|
|
| |
Objects |
|
Manage data objects and their attributes |
| |
|
|
Define the datatypes of each attribute
for the selected database |
| |
|
|
Use Practicum "AutoTypes"
which allow for automated entry of attributes with predetermined
datatypes, based on suffix of the attribute name |
| |
|
|
|
| |
Relationships
|
|
Define the business and entity relationships
between each of the data objects in the system |
| |
|
|
|
| |
Anomalies |
|
Identify errors and omissions in
the system design for each design component. |
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
Software Requirements |
|
| |
|
|
|
|
|
| |
Operating
System |
|
Windows 98, NT, ME, XP, and 2000
|
|
| |
|
|
|
|
|
| |
Processor |
|
Pentium 3 - 500 MHz or higher |
|
| |
|
|
|
|
|
| |
RAM |
|
128 MB RAM minimum |
|
| |
|
|
|
|
|
| |
Disk Space |
|
20 MB free hard disk space |
|
| |
|
|
|
|
|
| |
Display |
|
1024 x 768 display resolution recommended
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|