1 In the context of a business information system to be developed, what is a user requirements?

2 Outline four major elements or issues or benefits of an Object Oriented approach to developing information systems. 3 Explain briefly how an Object Oriented approach can lead to improved quality and faster development. 4 How does an Object Oriented approach help in re-using previous work? 5 What is Feature Creep (or Shifting Requirements)? Why is it essential to manage user expectations. 6 Give two reasons why a user may want a system replaced or enhanced when it is working satisfactorily. 7 How could UML be useful, within a Systems Development Methodology? 8 What is a life cycle model? 9 When there are disadvantages in the Traditional Life Cycle, why is it still used? 10 Why is UML not considered to be a Systems Development Methodology? 11 List three disadvantages of the Traditional Software Development Life Cycle? 12 Taking two disadvantages of the Traditional Software Development Life Cycle, explain how these are addressed in the Unified Process. 13 Explain the purposes of Interviewing, Questionnaires, Documentation and Observation. 14 What is a Functional Requirement? 15 State two advantages in using software tools such as yUML and Violet UML. 16 What is UML? 17 Why is UML referred to as a Visual Symbolic Language? 18 Why is it necessary to define user requirements accurately? 19 What is a Use Case? 20 What is meant by the Realisation of a Use Case? 21 Define what is meant by an Actor in relation to a Use Case Diagram. 22 Distinguish between the terms Use Case (UC), Use Case Diagram (UCD) and Use Case Model. 23 A Use Case Diagram should be like a road-map. Explain why this is the case. 24 If a Use Case Diagram is like a road-map of a system, give two examples of other diagrams giving the details. 25 Explain how an Essential Use Case Model helps to define the scope of the system. 26 Why is it necessary to define the context or domain of a system? How do you show the domain in a Use Case Diagram? 27 Distinguish between the relationship between an Actor and a UC in a UCD and the relationship between Use Cases?

28 A Use Case is a User Requirement clarifying who is involved and what is wanted by the user. Give an example of a User Requirement explaining who is involved and what the user wants. 29 A Use Case Diagram helps to clarify user requirements with users but a developer will need a Class Diagram to clarify things. Explain why this is true. 30 Explain why Use Cases are considered to be an informal and imprecise modelling technique. 31 Explain why a Use Case Diagram may not capture all the requirements. 32 Sketch a diagram or diagrams to illustrate (i) Generalisation between Use Cases (ii) Generalisation between Actors. Explain how (i) might lead to (ii) - or the reverse of this. 33 Why is it that a Use Case Diagram does not capture how a system works. List two diagrams which should indicate to a designer how a system is expected to work. 34 Explain clearly why even an outline description of a Use Case would always contain a verb (an action word). 35 If you do not show logic in a UCD, given an example of a diagram where you would show the logic relating to a UC. 36 Why do you need to document or describe a UC in some detail? 37 Outline three ways of describing a Use Case in detail. 38 What is the significance of << include >> relationship in a UCD? 39 Distinguish between << include >> and << extend >> relationships in a UCD. 40 Other than << include >> and << extend >> give an example of a relationship between Use Cases. 41 Where does an Extension Point appear in a Use Case Diagram? Give an example. 42 Draw a sketch of a possible example to show how the concept of Generalisation Specialisation can be used with (a) Actors (b) Use Cases. 43 What is a Class? Give a definition of a Class. 44 What is the significance of a EntityClass Stereotype. 45 Describe (a) the similarities (b) significant differences, between an Entity in an Entity Relationship Diagram (ERD) and a Class in a Class Diagram (CLD). 46 What is the significance of a User-Interface or Boundary-Class Stereotype? 47 In addition to Entity-Class Stereotypes and Boundary-Class Stereotypes, why do you need Control Stereotypes? 48 What is the difference between the terms Class and its Objects 49 List four characteristics that distinguishes a Class Diagram from an Entity Relationship Diagram. 50 Give an example to illustrate a is a kind of relationship between classes. 51 What is an Abstract Class? Give an example.

52 What is the difference between an attribute and an operation (in a class definition)? 53 What is the relationship between the attributes and the operations contained within a class? 54 Explain why an Abstract Class will not have real life objects. 55 What are the advantages of treating two related Classes as Subclasses of a Superclass? 56 In Class Diagrams, what is Aggregation? What is the UML notation for aggregation? 57 In Class Diagrams, what is the difference between Aggregation and Composition? Give an example of each. 58 Why might aggregation (or composition) be referred to as a whole-part relationship. Give an example? 59 Why might generalisation be referred to as a kind-of relationship? 60 Use an example to illustrate the notation for generalisation. 61 What is an Association Class? 62 What is equivalent or similar to an Association Class in an ERD? 63 Distinguish between an Object and a Class. 64 Explain what is meant by the noun extraction method of finding Classes. 65 Why draw Object Diagrams? 66 How does Object Diagrams differ from a Class Diagram? 67 What is a stereotype in the context of Classes? 68 Explain four relationships that you can show in a Class Diagram. 69 What is an Association Class? 70 A Link-Entity in an Entity Relationship Diagram is similar to a Association Class in a Class Diagram. Give an example to illustrate. 71 What is multiplicity? 72 Explain the difference between a 1-many and many-many relationships in a Class Diagram or an Entity Relationship Diagram. 73 What is the relationship between the attributed in a class and its operations (or methods)? 74 What is the connection between a Sequence Diagram and a Use case Diagram. 75 Why is it necessary to have a Class Diagram before you construct a Sequence Diagram? 76 Why is it necessary to find or define Use Cases before starting to construct a Sequence Diagram? 77 Either list the components of a Sequence Diagram or alternatively, provide a labelled diagram to show the components. 78 Give an example of a construct in a UCD which should help in constructing a Class Diagram.

79 How does a Use Case Diagram help in constructing test specifications. 80 Name two UML diagrams that depend on previously defined or identified Use Cases. 81 What is a State Diagram? Explain clearly what a State Diagram models. 82 Give an example to explain what is meant by the term State in a State Diagram (or State Chart Diagram). 83 Name the parts of a Sequence Diagram. Explain their significance. 84 List two important uses or functions of sequence diagrams. 85 What is a Design Pattern in Object Oriented Analysis and Design? 86 Why use Design Patterns? 87 Give four headings for documenting a Design Pattern. 88 Name the phases of the Unified Process. What are the objectives of these phases. 89 What is the Traditional Paradigm? 90 What is a Rapid Prototype in Software Development? 91 Distinguish between the phases of the Unified Process and the steps or stages of the Waterfall Systems Development Life Cycle. 92 Briefly explain the similarities in some instances and contrasting difference in other cases between the Traditional Systems Development Life Cycle (Waterfall Model) Stages and the Unified Process Phases. 93 Is there a place for Rapid Prototyping in the Unified Process? 94 Explain why Project Inception using the Unified Process could be completed in one pass, Elaboration Phase may require a number of iterations. 95 Explain briefly, the concept of Swim Lanes in the context of Activity Diagrams. 96 Explain what is meant by a Work Breakdown Structure (WBS). Why is a WBS important in project planning. 97 Explain the difference between system scope or context and project scope. Why is it important to consider each separately? 98 Given that the phases of the Unified Process are Inception, Elaboration, Construction and Transition explain the objectives of these phases 99 The Inception Phase in the Unified Process often can be completed in one attempt whilst the Elaboration Phase may require repetition or iterations. Give examples of activities carried out in the Inception Phase and those that are repeated the Elaboration Phase. Briefly explain your reasons. 100 List the reasons why an Information Systems Development Project could fail. 101 Describe briefly four project management roles and four responsibilities of a project manager. 102 Give four reasons why studying for this module can be considered to be a project. 103 Draw a sketch to show what a Gantt Chart represents. 104 What is a Risk Matrix? Why is it necessary to identify risks.

105 Who are the primary types of stakeholders who should be considered during project inception? 106 Give examples of four types of risks that you may encounter during a Information Systems Development project. 107 Explain two external responsibilities of a project manager outlining their significance in the planning/management process. 108 Taking suitable examples of project activities, give two examples of activities that can be done in parallel. Give an example of an activity that needs to wait for an outcome before commencing, 109 Why do many projects end up having unreasonable deadlines? How should a project manager react to unreasonable demands? 110 List three points which should be contained in a definition of Project Management. 111 List two things which should help a manager to ensure project success. 112 List four objectives of the Inception Phase of the Unified Process. 113 The Inception Phase in the Unified Process often can be completed in one attempt whilst the Elaboration Phase may require repetition or iterations. Give an example of an activity that is carried out in the Inception Phase and the Elaboration Phase, explaining briefly the reasons for repetition. 114 Giving examples, distinguish between the terms Internal Responsibilities and External Responsibilities of an Information Systems Project Manager. 115 Who are the primary types of stakeholders who should be considered during project inception? 116 What are the four phases of the Unified Process? 117 Describe briefly four techniques for identifying WBS tasks. 118 What are the differences between a top-down WBS and a bottom-up WBS. 119 What is the difference between a Template and Analogy WBS. 120 Briefly explain the following terms (i) Critical Path (ii) Slack time or Float and (iii) Milestones. 121 Taking your group coursework as an example briefly discuss the importance of teams in relation activities that can be undertaken in parallel. Why are milestones important in organising a team project. 122 Discuss briefly Brooks Law: Adding more people to a late project will make it run even more late. 123 Successful teams contain a mixture of specialist skills and personality types. Discuss briefly. 124 What is the purpose of Feasibility Analysis. List four activities that you would undertake to evaluate project viability.

125 Explain briefly what is meant by Cost Benefit Analysis. Give two possible examples of possible cost savings relating to a new system or an enhanced system. 126 Briefly discuss what is meant by Risk Analysis. You may use any example including your group coursework project. What steps would you take to counter risks. 127 Adaptive projects are very susceptible to schedule risks. Discuss briefly.