Forum Categories
Online Timesheet System Requirements
These are the requirements for the development of the Online Timesheet System project done in NSU's CSIS4310 - Distributed Data Processing course
Category nameThreadsPostsLast post
Brief description that defines the goals and the scope of the project.
00 
Given our general problem statement, we can break this down into the following feature set or business requirements list.
00 
Shows a picture in UML of the domain model for our application. It should have all the data entities and their relationships, but no attributes.
00 
By developing prototype screens early on, you put a face to the application, which gets people excited and motivated to get the application built. This is also a good way to eliminate many of the cosmetic changes up front (such as fonts, colors) and come up with an agreed upon consistent look and feel that can be implemented using cascading style sheets (CSS).
00 
UI flow diagram or website map, is a picture, essential to show a navigation map of the various screens created in the previous "User Interface (UI) Prototype"
00 
Formal use cases (User Stories) can entail a page or two of requirements with preconditions, postconditions, success/basic path, failure/alternative path, and other sections for each use case. Here we will just include a numbered list of User Stories with their name, description and priority.
00 

Show hidden

rss icon RSS: New threads | New posts

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License