Requirements, Design and System Specifications by Phoebe Barnett https://padlet.com/phoebe_mb/fmx540801hl3 OCR A2 Level ICT G063 - Phoebe Barnett en-us 2016-01-21 10:43:37 UTC 2025-09-25 16:05:24 UTC hello@padlet.com http://www.clipartlord.com/wp-content/uploads/2014/09/desktop-computer18.png System Specification phoebe_mb https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426839 The system specification defines the requirements for the new system. These include, for example, the facilities and outputs that the new system should provide. The requirements are developed and formulated from the results of the investigation of the current system.

The system specification should include:

  • operation requirements: what operations the system should carry out
  • information requirements: what information the system should provide to the end users
  • volume requirements: for example, how much volume of processing is to be handled
  • general systems requirements: for example, the degree of data accuracy needed, security issues, the need for an audit trail, the flexibility of the system and its ability to adapt to growth and change etc.
]]> 2016-01-21 10:45:28 UTC https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426839 Design Specification phoebe_mb https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426861 The design specification is usually developed by the systems designer. The specification is usually created following the investigations. The contents of the design specification may have a different focus dependent on the type of stem that is being developed. For example, if a website is being developed, then it would be appropriate to include the links between the webpages and how these pages would be organised.

This would not be appropriate if a database system is being developed. However, both the website and the database might include data entry forms. The design for the data entry forms would be included in the design specification.

The design specification usually includes:

  • the purpose of the system
  • assumptions, limitations or constraints
  • the inputs - documents and screens/interface
  • the outputs - documents and screens/interface
  • error messages
  • the colours/fonts/sizes, including the consideration of the corporate image/house style, to be used
  • validation rules
  • processing requirements/queries
  • data structures
  • modelling diagrams
  • the hardware
  • the software/programming language to be used
  • test plan/
]]> 2016-01-21 10:45:37 UTC https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426861 Requirements Specification phoebe_mb https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426885 The requirements specification is usually developed by the systems analyst. It will be developed following investigations that have been carried out on the system.

The requirements specification should clearly define what the system is to do and how this should be achieved. It should also describe all the interactions the users will have with the software.

The defined functional (what the end user wants the system to do) and non-functional (the end user defined limitations relating to response time/hardware/software/programming language) requirements should also be included within the requirements specification.

The contents of a requirements specification will also include:

  • the objectives/purpose of the system
  • the scope of the system
  • the proposed timescale for the project
  • end-user defined constraints including budget, time, hardware and software choices
  • a contract.
]]> 2016-01-21 10:45:47 UTC https://padlet.com/phoebe_mb/fmx540801hl3/wish/90426885