Objectives: The purpose of this lab is to gain some fluencies with technical specifications, including:
- Creating Technical Specifications
- Evaluating Technical Specifications
The Project Charter is a high level document that is considered the “Needs” document. The Functional Specification is a lower level document from the Project Charter that documents the behavior of the software. And the Technical Specification will be the lowest level document that will discuss the details of the coding for that piece of functionality.
So, as you see, we have a process here in software engineering that gathers the initial high level requirements from the client and hands these off to another software professional called a Business Analyst. The Business Analyst will message the requirements and ultimately create the functional specification. The functional specification is then handed off to the developers who will then create the technical specification. The technical specification will be the blue print used by the developers to create the code for the specified functionality.
Assignment Directions:
Using the example document (attached)
Fill out the following table for a login feature for the Hovitar
You must have at least five rows.
Needs (Charter) Behavior (SRS) Design (SDS)
Vision and Scope Document Software Requirements Specification Design or Architecture Document
The users need to be able to log in with magnetic strip card
The users who are logged in with magnetic strip card shall be verified with fingerprint scan
If log in with magnetic strip card fails, verify user with retina scan
If anything has failed, users need to log in with username and password
If wrong username and password enter for 3 times, disable log in for 5 min