CSC408F/CSC2105F Software Engineering Fall 2004/2005Mid Term Test (15% of course mark) October 28, 20041. (15%) You are the chief architect in a software company. Can you explain when you can apply“Web Services” in software development, and when you cannot? Name 3 software in yourcompany that can be reengineered with Web services, and 3 software that cannot. Supportyour arguments with +/- evidences.Answser.4% (a) Use “Web Services” when the software development desires or has:(1) high interoperability (or protocol standardization) w/o -2(2) high reusability (or components-off-the-shelf (COTS)) w/o -2(3) componentization (or modularization, information hiding, large-scale complexity,need for middleware ) with +0.5(4) dynamic matching or deployment (or networked) with +0.53 x 1.5% (b) 3 example software satisfying the above requriementsFor each example (1.5%):the mark = min(1, (satisfaction mark / 4))Where satisfaction mark is determined by criteria in bullet (a).Example. A heterogeneous database system needs high interoperability (2%) and highreusability (2%), needs to hide implementation details (+0.5%). Since it has 4.5%, 1mark is earned.Explained with positive/negative reasons. w/o -0.52% (c) Do not use “Web Services” when the software requires(1) demanding performance (or real-time) w/o -1(2) can not use any net protocol (or extreme high security) w/o -0.5(3) too simple (or single component, no need for middleware) w/o -0.53 x 1.5% (d) 3 example software satisfying the above requriements (similar to marking scheme in (b),replace criteria (a) with criteria (c))2. (15%) What are the risks in a software development? How to evaluate the risk of an earth-quake to the software development? Name 4 risk factors in the OmniEditor project and indi-cate measures that can prevent or mitigate them?Answser.3%(a) Give a definition of the risk in software development (w/o -2) and list some commonrisks (w/o -1).2%(b) Give the reasoning for the earthquake risk (w/o -2):Impact is big to personnel, small to software storage (w/o -1); Probability is very small(w/o -1).4x2.5%(c) Sum risk factor mark for at most 4 factors. Each factor is marked by:(1) relevant to OmniEditor (w/o -0.5)(2) impact analysis (w/o -0.5)(3) probability analysis (w/o -0.5)(4) risk factor prevention or mitigation (w/o -1)3. (15%) A competitor company A has a killer application K that dominates the market. You arerecently employed by company B as a senior consultant, their application Kalways has allthe functionalities of K. What technical advices will you give to help take away K’s marketshare?Answser.5%(a) Quality (non-functional issues) improvements, w/o -55%(b) Break down of the quality into a number of issues, such as performance, usability, se-curity, etc. w/o -55%(c) Study the company A’s software, find its weakness, w/o -5(d) Measuring the qualities attributes +1(e) Open-source or use open standard with +1(f) Give a concrete and reasonable example +14. (25%) You are managing the development of a large-scale software system which alreadyhas Y out of X components developed. According to your project estimation, the undevel-oped components still need T person-month to finish, while you just have N team membersincluding yourself. Now you are pressed to complete the system within as short as S monthsand you can and only can recruit M more junior developers. Will you meet the time pressure?If you can, how will you reorganize the team? If you cannot, why? Please answer accordingto the following three scenarios:X Y T N S M----------------------------------------------------(1) 3 2 9 5 2 5(2) 30 2 100 5 2 50(3) 3 0 15 5 1 0Answser.5%(a) Use the numbers in estimating the time needed for the new project w/o -54%(b) Scenario (1) is not feasible because the time available is below 75% of the estimatedtime; otherwise -44%(c) Scenario (2) is feasible by the estimation, if hierarchical team organization is used; it isnot feasible if training efforts is huge by explicit assumption; otherwise -44%(d) Scenario (3) is not feasible because the time available is far below 75% of the estimatedtime; otherwise -44 x 2%(e) If the calculations in the discussions make following mistakes, such as: mistake “person-month” for ”month”.-2 per mistake: if there are more than 4 minor mistakes, -8.5. (30%) Here is a list of unfinished requirements specifications for the ”Meeting Scheduler”system (including software and human as parts of the system):Functional Requirements Non-functional Requirements--------------------------------------- ---------------------------0. Schedule Meeting 1. Minimal effort0.1 Collect Timetable 1.1 Collection effort0.1.1 By Person 1.2 Matching effort0.1.1.1 By email, fax and letters 2. Good Quality0.1.1.2 By email 2.1 Minimal conflicts0.1.2 By System 2.2 Good participation0.1.2.1 Have updated time table0.1.2.2 Collect them0.2 Choose Schedule0.2.1 Manually0.2.2 Automatically(a) For each functional requirement to the left, express its goal, input, output, pre/post con-ditions, exceptions.(b) Relate the tasks at the left hand side with the criteria at the right hand side using positive[+] or negative [-] relations (E.g. 0.1.1 [-]1.1), then indicate which functional tasks areneeded to fulfil the top level requirements “0” and “1”, regardless to “2”.Answer3% (a) If not all functional requirements are expressed, -32x3%(b) For 0, 0.1.2 (AND decompositions): check if a parent goal’s precondition implies thefirst sub goal’s precondition (not -1), and the first subgoal’s postcondition implies thesecond subgoal’s precondition (not -1), and the second subgoal’s postcondition impliesthe parent goal’s postcondition (not -1).3x2%(c) For the 0.1, 0.1.1, 0.2 (OR decompositions): check whether each subgoal’s postcon-dition implies the parent goal’s postcondition (w/o -1), and the parent’s preconditionimplies the subgoal’s precondition (w/o -1).10%(d) For the second question, check list:0.1.1 or0.1.1.1, 0.1.1.2-[-]-> 1.1, w/o -20.1.2 or0.1.2.1, 0.1.2.2-[+]-> 1.1, w/o -20.2.1 -[-]-> 1.2, 0.2.2 -[+]-> 1.2, w/o -20.2.1 -[-]-> 2.1, 0.2.2 -[+]-> 2.1, w/o -20.2.1 -[+]-> 2.2, 0.2.2 -[-]-> 2.2, w/o -25%(e) if 2 is not concerned, one can remove the last 4 relations and prune the functionalrequirements based on the other relations. The resulting functional requirements shouldonly have:0, 0.1, 0.1.2, 0.1.2.1, 0.1.2.2, 0.2, 0.2.2If the answer has only the