INF 3705 EXAM PACK PAPER SOLUTION. BEST FOR EXAM PREP.

TABLE OF CONTENTS CONTENT OCTOBER /NOVEMBER 2019 MAY/JUNE 2019 OCTOBER/NOVEMBER 2018 MAY/JUNE 2018 OCTOBER/NOVEMBER 2017 MAY/JUNE 2017 OCTOBER/NOVEMBER 2016 MAY/JUNE 2016 INF 3705 2 | P a g e 3 | P a g e May June 2017 Question 1 You are a software engineering manager and your team proposes that model-driven engineering should be used to develop a new system. What factors should you take into account when deciding whether or not to introduce this new approach to software development? Answer: The factors that you have to consider when making this decision include: 1. The expertise of the team in using UML and MDA. (Is expertise already available or will extensive training be required.) 2. The costs and functionality of the tools available to support MDA. (Are tools available in house or will they have to be purchased. Are they good enough for the type of software being developed) 3. The likely lifetime of the software that you are developing. (MDA is most suitable for long-lifetime systems) 4. Requirements for high performance or throughput (MDA relies on code generation that creates code which may be less efficient than hand written code) 5. The long term benefits of using MDA (are there real cost savings from this approach) 6. The enthusiasm of the software developers. (are all team members committed to this new approach) Question 2 Software specification Software specification is the process of establishing what services are required and the constraints on the system’s operation and development.√ Therefore, the requirements engineering process include the following: 3 | P a g e 4 | P a g e • Feasibility study: Is it technically and financially feasible to build the system? √ • Requirements elicitation and analysis: What do the system stakeholders require or expect of the system? √ • Requirements specification: Defining the requirements in detail√ • Requirements validation: Checking the validity of the requirements√ Software validation Verification and validation (V & V) is intended to show that a system conforms to its specification and meets the requirements of the system customer. √ • It Involves checking and reviewing processes and system testing. √ • System testing involves executing the system with test cases that are derived from the specification of the real data to be processed by the system. √ Software evolution Software is inherently flexible and can change. As requirements change through changing business circumstances, the software that supports the business must also evolve and change√. Although there has been a demarcation between development and evolution (maintenance), it is increasingly irrelevant as fewer and fewer systems are completely new√