2.4 Documentation Before beginning any of the phase testing, it was important that I knew about

Describe how to complete and maintain documentation in accordance with organisational procedures, in relation to:

It is a requirement that all hand written records must be written in black ink, clear and concise and contain only facts, no personal opinions are to be recorded in care plans as this is deemed unnecessary.

records must be taken of what has been said by the individual; these records must also include the date, time and place

* Make a written objective record that includes time and date, exact words as far as possible, the name of the person to whom the concern was reported, the name of any other person present at the time of observation or disclosure.

recommended to use black ink. Some documents will only accept black ink. Information must not be crossed out, or covered using correction fluid.

A set of preliminary usage scenarios that describe the use of the system under different operating conditions.

This section gives the details and specification of the software on which the system is expected to work.

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

The purpose of this section is to identify the documentation that will be used for ensuring quality.

3. A Use Case is developed to support requirement specification. It is a detailed description of specifications in its simplest form using Realtime scenarios of the functionality requirements between the actors and

The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.

This will help me and the team to understand how the system works. The documents will serve as the reference point on the basic requirements. For cohesiveness, I will have the team to discuss my findings during meetings (Trotter & Uhlman, 2011).

of events which I am going to look at to see if there was a single

A FedEx employee picks up the customer’s box and scans it so FedEx recognizes it. Now the product is registered and traceable. The product is then taken to a sorting center where it is classified according to its destination. The package is put on a belt where it is measured and a price tag is determined. In the next step, the packages are put into containers. These containers are loaded in aircrafts directed by a control

All paragraphs, heading and graphics are consistent with all material that has been developed in this manual. Graphics are simple and can be easily followed.