iii) User of the product
Hands on users – people who operate the product and number of simultaneous usersPriorities assigned to usersUser participation – an estimate of needed involvement in the projectUser classes may vary as an end-user, super user or administrator with there specificcharacteristics.
Here, will describe the details of who is the beneficiary of this system that may be client perspective, administration point of view, end-user point of view, planner point of view or etc.
Limitations of the system in terms of number of transactions, batch processing, hardwareconfiguration and etc.
vi) Critical success factors
In order to make development successful, enlist the critical factors and taken intoconsideration while going through software development life cycle.
2) Architecture about flow of the system
It would deals with what way data is to be processed and information has to be passed to thedestination through bridges, routers or hub etc.
3) Project constraintsi) Mandated constraint
Solution design constraint Implementation environment of the current system Partner or collaborative applications to be used by the product Off the shelf software used within the product Anticipated workplace environment Project duration budget Financial budget for the project
ii) Relevant Facts, Assumptions and Dependencies
Factors that have an effect on the product but are not mandated requirements
Assumption the team is making about the project
46.7 System Objectives
The system objectives should cover the business objectives and the quality objectives, as far as possible in full detail and in measurable terms.This process tries to ensure that all aspects necessary to satisfy the customer's need regardingthe deliverable software and associated accessories are defined and/or mentioned. All suchobjectives could be addressed in this section.As a guideline to write these objectives, the following points must be considered