1.1.1 Identify the context for which a new system is planned

Before a system is designed, it needs to be identified what the system should do. To do this is the job of the systems analyst. He looks at the existing system and tries to observe how it works. This can be done using surveys, interviewing users, observing them or by tracing how information is handled by looking at the documents produced by it.

For this, the systems analyst has to factor in a number of things: what existing infrastructure from the existing system can be used? What requirements on hardware and software will the new system have? Are there any ethical issues resulting, for example will the new system make people unnecessary, leading to loss of jobs?

Data Collection

1.1.2 Describe need for change management

Without a proper plan on how the new system will be implemented once it is designed the change from the old system to the new one will not be successful. Many factors will need to be regarded:

1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers

Without a proper plan on how the new system will be implemented once it is designed the change from the old system to the new one will not be successful. Many factors will need to be regarded:

1.1.4 Compare the implementation of systems using a client’s hardware with hosting systems remotely.

Software as a Service (SaaS): The client does not run its own computer system to handle operations, but lends servers from the software manufacturer that are managed and maintained by the software manufacturer. A great example is SAP.

Advantages

Disadvantages

1.1.5 Evaluate alternative installation processes.

1.1.6 Discuss problems that may arise as a part of data migration

File formats are another worry when concerning the issue of data migration and compatibility. Having the ability to read and write data in the same manner as before, following an improvement or change in a system, is almost certainly the fundamental aspect which is taken into consideration.

Incompatible file formats

Incompatible data structures

Changed units leading to misinterpretation (new system interprets temperature in °C instead of °F)

1.1.7 Suggest various types of testing.

esting is very important in developing a computerized system, as it tries to ensure that the system works as expected. A system that does not work as expected (it is buggy) greatly reduces productivity and end user satisfaction.

Testing is usually done in two stages: before the system is delivered and after it has been set up.
Testing in the first stage is often referred to as Alpha testing, while testing in the second stage is often referred to as Beta testing.

Alpha testing involves the engineers who develop the system testing it with data similar to real data while beta testing involves testing by real users with real data.

1.1.8 Describe the importance of user documentation.

User documentation is a crucial part of a system as it is the document that explains the working of the system to the user. A well-made user documentation guides the user through using the system and thus increases productivity. If the user documentation is simple, system implementation can happen faster because users require less training to learn how to use the new system.

Users are non-technical people, they only need to know how to use the system. Therefore, the user documentation does not involve detailed explanations of how the system works.

User documentation supports computer system users, including both hardware and software. Good user documentation can ensure that users are quickly able to adapt to a new system. Documentation is an important part of software engineering. Types of documentation include:

Different Types 

• Requirements - Statements that identify attributes, capabilities, characteristics, or qualities of a system. This is the foundation for all that is implemented.
• Architecture/Design - Overview of software. Includes relations to an environment and construction principles to be used in design of software components.
• Technical - Documentation of code, algorithms, interfaces, and APIs.
• End User - Manuals for the end-user, system administrators, and support staff.

1.1.9 Evaluate different methods of providing user documentation.

Help files: Files supplied together with the system. They can usually be called up with a button in the system.

Advantages

Disadvantages

Online support: Special web service hosted by the system’s developer to provide user documentation.

Printed manuals: manuals printed on paper and supplied together with the system.

1.1.10 Evaluate different methods of delivering user training.

Training staff in using a new system is very important as productivity greatly depend on how familiar users are with a system. Therefore good user training is an essential part of introducing a new system.

Self-instruction: users reading a manual or watching a tutorial, or randomly doing something in the system to figure out how it works. This type of training is only suitable for experienced computer users as they are more confident to start using an unfamiliar system alone to figure out how it works.

Formal classes: users sitting in a classroom listening to an instructor who shows and explains how to use the system. This type of training is useful to train large amounts of staff as it is effective and relatively cheap, but if the size of the classes is too big, there is little time to deal with individual problems and questions.

Remote/online/personal training: an instructor training a single user either by being in the same room or by some kind of remote connection (Skype, chat). This is the most effective way of training as training can be suited to user’s needs and abilities, but is very expensive compared to other types of training.