Part 1 :
After reading the three Objectives samples provided, these are my ranking from best to worst: Sample 2 Healthcare, Sample 1 Safe House, Sample 3 Website redesign.
What's good about Healthcare:
In the sample 2, it explicitly tells the difference between functional and non functional requirements. The use of the word "must" conveys a message that these items will be done. The functional requirements were unambiguous and concise. In the Applicable standards section, it specified how the HIPAA regulation affect their system.
What could be Improved:
Certain firmware and Android version terms used can be difficult for a novice to understand. Therefore it will be beneficial to use simpler terms.
What's good about Safe House:
They specified which platforms their application should work. They gave details and consequences of not following Clergy act.
What could be Improved:
They include some implementation details which could be avoided.
What's good about Website Redesign:
Sets some framework required for the usage of the system.
What could be Improved:
The website redesign was ranked the worst because the objectives were not completely clear. They included certain implementation details that was not supposed to be stated in the objectives. The objectives were unclear and ambiguous
Part 2 :
Sample 1: Safe house - The main difference between version 0.1 and the final version is the breakdown of the categories. This makes it visually easier for the reader to understand the objectives more clearly and specifically. The final version has used parallelism which made more easier to read. They have removed the details about the expansions and made the section more rich.
Sample 2: Healthcare - The difference between version 0.1 and the final version is in the increase of the details. They have made each item in the functional and non functional requirements section more specific. They have expanded on the acceptance criteria. In the applicable standards sections they specify how HIPAA will affect their application and what they will do about it instead of just stating it.
Part 3 :
Many of you rely on the bus system to get from one class to another, or to and from your dorm. We believe it would be beneficial for you to have a way of knowing if a bus is available at a particular stop at the time you would be needing it. The mobile application that we create will use data from your own schedule to send notifications after your class ends about available buses and routes you could take to get to your next destination in the least amount of time. There are existing applications which allow a student to check the status of the GT bus system at any given time, but our application would automate this information – providing it to you as soon as you get out of class.
1) Students have short time to get to classes
2) A user interface that would make it easy for the students to locate the buses
3) Incorporation of student schedules
4) Notifications on bus routes, faster routes and arrival, departure times
No comments:
Post a Comment