Systems Lifecycle

A computer system in industries such as manufacturing, finance and retail have a specified life span The results from one stage are used to inform the work on the next stage in the cycle at any

stage it may be found necessary to return to re-evaluate a previous stage.

Problem definition, Feasibility, Analysis, Design, Development (coding) and Testing, Implementation, Maintenance, Evaluation

Current software is outdated Current hardware/technology is outdated Current system is too slow/response times are slow for the user Current software does not perform its required task Current interface is not user friendly Compatibility with other systems (e.g. merger, Govt) The company is expanding due to more customers Change in legal requirements

Fact finding (questionnaire/interview/record inspection / observation) is carried out so that the following can be produced: A description of how the current system works Identification of existing problems Solutions to resolve the problems Production of a requirements specification ( resources required for the proposed system). These include

Detailing inputs needed and outputs required Specifying user requirements Hardware/software needs

Advantage: Analyst can get a broader view of the processes Analyst can get a feel of user competence and abilities in doing a task Analyst can get idea of time required to do a task Does not require employee to leave their job Disadvantage: Users may respond differently if they are being observed Lack of interaction between analyst and user

Advantage: Questions can be modified according to answers given User can express their opinions in a detailed way More factors may come to light as the user answers questions User may feel valued by the personal nature of interview Analyst and user can build up a working relationship Disadvantage: Time consuming for analyst to gather facts Users may not tell the truth if they feel intimidated Suggest answers the analyst may want!

Split into pairs: interviewer and interviewee. Design some questions to assess your interviewees suitability for running an extracurricular activity. Present your results to the class.

Advantages: A lot of data can be collected in a short period of time Efficient in terms of time Useful when a little information is required Not difficult to complete Direct data entry/OMR/can be distributed electronically Disadvantages: Difficult to design Inflexible opportunities to respond Low return rate from target audience

Design a questionnaire to assess the ICT skills of a parent, sibling or friend (not in this class). Remember, you are not to ask the questions. Give them the paper and do not assist them.

Advantage: See how data flows through the system and is processed Analyst can get an idea of the volume of data stored See how data is collected/stored Can inspect how data is verified/validated Disadvantage: Limited interaction with potential users Time consuming.. . if there is a large volume of files

HCI software is designed to allow the user to communicate with the PC Good interface design should be: user-friendly and therefore effective, efficient and satisfying for the end user. With a design phase this is unlikely to occur. When designing the interface it is important to remember who the user is and consider features such as shortcuts for expert users and tooltips / online help for beginners A consistent design and logically ordered interface is important or the user will be confused. e.g. buttons should be in the same place on each screen The type of user should be considered Amount of information displayed should not be too much and cause information overload

Input specification (e.g. Data Form layouts) Process specification (e.g. Queries, calculations) Output specification (e.g. Report layouts) Test planning and sample data (e.g. normal, abnormal, extreme) Data flow diagrams (flow of data through the system) Data structures (e.g. Entity Relationship Diagrams, data dictionary) Macros or Pseudo code (e.g. Algorithm design) Validation and verification routines Hardware and Software Requirements

Ensure text boxes are appropriate sizes for data entry e.g. Address text box would be larger than DOB text box Use drop-down menus where possible to show alternatives Include buttons such as next, previous, submit, clear, close, help Include a title outlining the form / document you are designing Ensure a good use of space and consistent layout

This involves checking data, done by the computer automatically at the input stage Its purpose is to reject data that does not conform to certain rules and ensure that it is reasonable

Examples of validation include: Range check - Check lower and upper limits of data value Existence check / lookup check - To check that the data appears / exists on the computer system Format / Character type check - To check all characters are of the correct type Field length check - The number of characters entered is within the pre-defined limit / 4 digits Presence check - To check that data has been entered Integrity/ cross field check - Confirming the value of a piece of data by comparing it with other data

Used with credit cards, ISBN numbers Extra digit, calculated from the number Weights are added to each digit Sum of the products is calculated Modulus (11) arithmetic is used 11 R will give check digit Exceptions to rule, if R=1 or R=0

Verification is used to reduce the number of errors that occur when data is input Double entry e.g. Please enter your email address twice and compare the two (either after the entry or during entry) Enter the data and visual compare it to the original data source (i.e. proof-read)

An electronic general knowledge game displays the following: a question four possible answers a clock to allow a set amount of time to answer the question a score (which is added to if the question is answered correctly) the score required in order to win the game. The player touches the answer that they want to input as their choice.

(Q) Using a pen and paper design a suitable layout to present the five areas. Once design use the Visual Basic toolbox and form to create the interface design.

A Computing student has written a program which stores and prints recipes. The program has a graphical user interface (GUI). (a) Describe how a good design of the GUI can make the program easier to use. (Note: Consider your own experiences with software)

Answer Easier to learn due to familiar layout and good use of online help will be intuitive Fewer mistakes will be made when using the program Input will be faster use of GUI objects such as drop downs/option buttons dialogue boxes to alert on validation errors No information overload / sensitive to the needs of the user

A antique book store would like a computer system created. The systems analyst has investigation and would like you to: design a system so that books, customers, sales, sales details are stored. create the tables, queries, forms, and reports using Microsoft Access

Evolutionary Part of the system is created and used to demonstrate the system to the user. Once the user gives some feedback regarding the prototype the remainder of the system can be created.

Throwaway The system, or part of it, is created using rapid development software and demonstrated to the user. Once feedback is given the prototype is discarded and the system is created from the beginning with the intended software development tool.

The purpose of testing is to prove that the system works. During testing, problems may be found, and amendments or improvements may need to be made. The testing process should be systematic and follow the strategy outlined in the design stage. This should ensure that all aspects of the system are working as outlined in the specification.

Write a plan of how you will test your book store database (i.e. include an explanation of normal, abnormal, extreme data). Enter some sample data and amend routines if testing identifies any issues.

Direct changeover/Big Bang Old systems stops and the new system begins No overlap between systems/no part changeover If new system fails old system cannot be used Parallel changeover Two systems run side by side for a period of time Comparing results of two systems can happen If new system fails, old system can be used

Pilot changeover New system could be used in a few areas of the business initially The results could be compared against the other areas that use old system Roll out the new system if successful/abandon the new system if unsuccessful Phased changeover / gradual changeover Each part of the existing system is changed over separately Each part can be tested separately May take a long time for the whole system to be changed over

Parallel Information is not lost/always a second copy Have to pay two sets of workers / overtime

Phased Still have most of system if things go wrong No expense of running two systems together Lose some data if things go wrong

Direct implementation/changeover Time is not lost, so ideal if rapid changeover is required e.g. End of academic year but before term starts Do not have expense of running two systems together If things go wrong lose all data Pilot running Pilot/phased/parallel are slow methods of implementation

Purpose (help programmers/analysts) make improvements to system/repair system/ maintain system (1) It should contain: Program listing Flowcharts/algorithms List of variables File structure Purpose of the system Screen layouts Print formats Hardware and Software requirements Test runs and known bugs Error messages Validation routines

Purpose help users to learn how to use system

It should contain How to load software/run software How to save a file How to search How to sort How to print How to add records How to delete/edit records Troubleshooting guide / Error messages Screen layouts Print formats (only if not mentioned in technical documentation) Hardware and Software requirements Tutorials

Suitability Does the system really provide a solution to the problem? Does the system meet the original user requirements? Does the new software integrate with the existing software? Effectiveness Does the system do what it is supposed to do? Does the system suffer from bugs? Are the access times for data retrieval acceptable? Is the hardware/software reliable?

Usability Do the users find it easy to use the system? Do the users require continuous training? Are the on-line help/tutorials useful? Do they have quick access to information? Do users save time not having to carry out tedious/repetitive tasks? Maintainability Will it be easy to maintain? Are there any shortcomings to be modified? Will new modules need to be added? Can upgrades be done on-line? Security of data Is the data secured against unauthorised access? Are the data/software backups taking place? Are users coping with passwords/user ids?