Question 1 1. a) Briefly explain what is meant by the term information system development method.

(7 marks) b) There are different approaches to software prototyping. Explain with the aid of diagrams the differences between throw-away prototyping and evolutionary prototyping. Which approach to prototyping can be merged with the waterfall software life cycle model and how? (9 marks) Rapid Method (see Appendix) includes five phases/stages: Feasibility study, Business analysis, Build usability and functional prototype, Refine prototype and Deliver prototype. Draw a diagram which shows the process of this method i.e. phases/stages and paths between stages. Use one way arrows to denote paths.

c)

Are Rapid Method prototypes throw-away prototypes or evolutionary prototypes? Justify your answer. (9 marks) Answer pointers 1.a) A collection of procedures, techniques, tools, and documentation aids which will help the systems developers to implement a new information system. A method will consist of phases (sub-phases etc.) which will guide the systems developers in their choice of the techniques which might be appropriate at each stage of the project and help them plan, manage , control and evaluate information systems projects (Avison, Fitzgerald) (7 marks) The diagram showing throw away prototyping (3 marks) The diagram showing evolutionary prototyping (3 marks) Throw away prototyping can be merged with the waterfall life cycle model. Typically it is used as a requirements gathering tool therefore it constitutes a part of the Requirements Analysis stage. (3 marks)
Feasibility Study

1.b)

1.c)

Business Analysis

Build usability and functional prototype

Deliver prototype

Refine prototype

Sequence of stages The main loop Small loops

(2 marks) (2 marks) (2 marks)

Rapid method prototypes are evolutionary prototypes as they initially focus on usability issues, next they are refined to include functionality, and finally they are refined to meet various non-functional requirements. (3 marks) Examiners Guidance Notes Only a small number of candidates answered part (a) well. Many discussed different types of methods or different software life cycle models, which of course was not required. Part (b) was answered by the majority of candidates well. However some candidates did not provide diagrams or the diagrams provided by the candidates were wrong. Most candidates answered part (c) well. Some candidates did not specify loops. A small number discussed DSDM instead. Question 2 2. a) Briefly discuss at least two similarities and two differences between Entity Relationships Diagrams (ERDs) and Class Diagrams. (6 marks) b) Rapid Method (see Appendix) specifies the development process, but it does not force a method user (i.e. developer) to use a prescribed set of systems modelling techniques. Assuming that you are required to use Rapid Method in your project decide which structured modelling techniques you would use in different stages of the method. Briefly justify your decisions. (9 marks) A Rich Picture is one of the main modelling techniques used in Soft Systems Methodology (SSM). Rich Pictures are particularly useful as a way of understanding the problem situation at the beginning of the project. They focus on various soft facts/aspects of the problem situation which are not represented by hard modelling techniques such as structured techniques, object-oriented techniques, etc. Which soft facts/aspects can be represented in Rich Pictures? (10 marks)

c)

Answer pointers 2.a) Similarities: Both diagrams show the structure of data in the system i.e. things (entities, objects) about which data should be stored Both diagrams show the relationships between these things (3 marks) Differences: In Class Diagrams there are 3 types of relationships: associations, aggregations and inheritance while in ERDs relationships correspond to associations Classes of course are semantically richer than entities as they encapsulate both the attributes and operations (entities encapsulate attributes only) (3 marks) 2.b) Feasibility study: Possibly the context and outline DFDs and high level ERD. Business analysis: More detailed DFD (showing main functions), ERD. Build usability and functional prototype: DFDs (updated), ERD (updated/expanded), EAPs (Enquiry Access Paths) and ECDs (Effect Correspondence Diagrams) for more complex functions, possibly ELHs and Structure Charts. Refine prototype: Possibly Structure Charts (for various subsystems) (9 marks) 2.c) Rich Pictures focus on subjective facts/aspects. The following aspects should be mentioned: points of view prejudices potential conflicts of interests political issues worries of individuals external interested parties major concerns At least 5 facts should be briefly discussed. (10 marks) Examiners Guidance Notes Many candidates managed to identify the main similarities and differences (part a). Part (b) caused many problems. A lot of candidates discussed UML techniques instead of structured techniques. Part (c) caused the main problems. In fact only a few candidates answered this part satisfactorily. Question 3 3. a) Assume that you are a project manager of five projects with the following characteristics: Project 1. A medium size business application whose requirements can be easily prioritised and grouped.

Project 2. A standard business application. You have developed similar systems in the past and expect to develop more in the future. Project 3. A complex real-time system whose requirements can be relatively easily identified and are stable. Project 4. A web-site for a local surgery. Requirements are vague and are likely to change in the future. Project 5. An order processing system with a web-site for a local business. Requirements are vague but stable (i.e. unlikely to change in the near future). Consider also the following software development approaches: waterfall, incremental, evolutionary prototyping, throw-away prototyping and component-based development. Which of the above approaches would you choose for each of your projects? Your choices should be properly justified. (15 marks) b) Explain the benefits of using a RAD approach to systems design. (10 marks) Answer pointers 3.a) Project 1: Incremental (requirements are grouped, so it is easy to identify increments) Project 2: Component-based development (components of previous systems can be used, and new components can be produced for future projects) Project3: Waterfall (No need for prototyping and requirements must be precisely specified) Project 4: Evolutionary prototyping (requirements are vague and unstable, so there is a need for rapid prototyping leading to the final product) Project 5: Throw away prototyping merged with waterfall (requirements are vague, so there is a need for prototyping, but they are stable, so the waterfall approach can be used to develop the back end sub-system in particular) (15 marks) 3.b) The following (or appropriate alternatives) would be expected: RAD approaches to systems design incorporate a high degree of user involvement within an IT project. This should mean that the developed system appropriately provides for user needs, since users have been consulted throughout the development of the system. (3 marks) RAD approaches to systems design emphasise the timely involvement of users in the development process, this can assist in ensuring that systems can be developed in appropriate time frame in order to meet with business needs. (3 marks) RAD approaches to systems design involve the use of prototypes which can allow for a more productive use of systems development staff, since there is less need for the production of highly detailed systems documentation. (4 marks)

Examiners Guidance Notes A number of candidates provided very good answers for part (a). Some candidates discussed recommended approaches in great detail, but provided insufficient justification of their choices. Most candidates provided reasonable answers for part (b), but many placed less emphasis on benefits and more emphasis on characteristics of RAD. Question 4 4. a) Your IT organisation has decided to introduce a new system development method for use in various projects. Your task is to identify possible problems and risks which may affect the introduction of the new method and the measures that could be adopted to avoid these problems and risks.

(16 marks)

b)

You have been asked to re-write a software application in a different programming language. As part of this process, explain how you would reverse engineer the software application. (9 marks)

Answer pointers

4. a)

The introduction of a new systems development method might fail because the staff using the method might not have been trained sufficiently in the method. In order to attempt to avoid this situation appropriate training techniques could be used such as short courses, computer based training packages (where available) or a train the trainers approach whereby a small group of staff are trained and then train the other staff. The implementation might also fail because there is insufficient on-going support for the use of the systems development method. This can potentially be avoided by having readily available documentation and training materials, and / or designated members of staff who will answer any queries regarding the use of the systems design method. The implementation of the systems design method might fail due to staff being unwilling to use the method or using it inappropriately. This can potentially be avoided by encouraging the staff to use the method, and incorporating the use of the method into quality control measures used within the organisation such as inspections and reviews. It is also important to involve the staff in the process of selecting a method (the staff should be consulted). Insufficient commitment to the new method by top management. The initiative of the introducing should be fully supported by top managers. Underestimation of costs associated with the new method. All the costs should be taken into account: documentation, training, tools, etc. The new method might be unsuitable for applications developed by your IT organisation. It is very important (when selecting a method) to make sure that the

method is suitable for your organisation. At least four possible problems/risks should be discussed. 4. b) (16 marks)

In order to reverse engineer the software application you would need to identify the systems components and their interrelationships. (3 marks) This would involve examination of any documentation, and examination of the coding of the application, and then matching this against input and output data for each of the modules in the system and for the system as a whole (to determine interrelationships). (3 marks) You would then need to create representations of the system in another form or at a higher level of abstraction. (3 marks)

Examiners Guidance Notes Most candidates answered part (a) well, showing an understanding of the possible risks when introducing a new systems design method and approaches for reducing such risks. Most candidates answered part (b) well, however, some candidates simply advocated using automated design abstraction rather than explaining how to actually undertake reverse engineering. Question 5 5. a) You are an IT manager who has recently introduced a new systems design method in your organisation. Discuss how your organisation could attempt to assess the benefits obtained through introducing the new systems design method. (10 marks) b) Discuss how software tools can be used to support systems design activities, explaining the potential benefits that they could provide. (15 marks)

Answer pointers 5. a) One approach to assessing the benefits obtained through introducing a new systems design method might be to compare the overall cost of developing a system using the new method with the cost of developing a similar system using the previous method. (4 marks) A different approach might be to compare the cost of maintaining a system developed using the new systems design method with the cost of maintaining a similar system developed using the old method (or no method). (3 marks) Another approach might be to compare the number and frequency of

implementation and post implementation problems encountered in systems developed with and without the new systems design method. (3 marks)

5. b)

Project management tools can produce project plans and schedules (e.g. gannt and pert charts) for design activities. Project management tools allow monitoring and tracking of design activities. (5 marks) Documentation tools can allow easy development, storage, retrieval and maintenance of system design documentation. Such tools may include a data dictionary facility. Documentation tools are useful for keeping systems design documentation up to date for future software maintenance activities. (5 marks) CASE tools can automate aspects of the development of design documentation and can in some cases generate code from the designs produced. CASE tools can often check for consistency between different design diagrams and documents, thus improving quality control, and helping to enforcing design standards in the design process. (5marks)

Examiners Guidance Notes Part (a) was generally answered well by most candidates, although some candidates provided only limited details regarding how the benefits would actually be measured. Most candidates answered part (b) reasonably well.