Information Systems Analysis and Design CSC340 V Goal Diagrams Goals and AND OR Trees Softgoals Building Goal Diagrams Diagrams How and Why Questions Questions 2004 John Mylopoulos Goal Diagrams 1 Information Systems Analysis and Design CSC340 Goals I I Goals represent business objectives for the new system and its operating environment For example Fulfill every book request Library organization Produce 1M MacG5s within a year Apple or Serve more passengers TTC 2004 John Mylopoulos Goal Diagrams 2 Information Systems Analysis and Design CSC340 AND decomposition Schedule meeting OR decomposition Generate schedule Collect constraints Collect timetables Collect other constraints Interactively Share timetables Manually Automatically Person collects From all From Initiator only By all means System collects By email 2004 John Mylopoulos Goal Diagrams 3 Information Systems Analysis and Design CSC340 Alternatives for Satisfying Goals I I I An AND goal is satisfied if all of its subgoals are an OR goal is satisfied if at least one its subgoals is An alternative solution to a root goal G consists of a set of leaf goals which together satisfy G There are 24 alternatives for the goal of the previous slide 2004 John Mylopoulos Goal Diagrams 4 Information Systems Analysis and Design CSC340 Softgoals I These are goals that are used as criteria for comparing alternative solutions for other goals E g Higher profits ProductionUnit3 Better service Satisfied customer User friend l y I n t e r f a c e 2 Portable Module4 2004 John Mylopoulos Goal Diagrams 5 Information Systems Analysis and Design CSC340 Usability User Tailorability Error Avoidance Information Sharing Ease of Learning User Flexibility Allow Change of Settings Programmability Modularity Allow Change of Colours Allow Change of State 2004 John Mylopoulos Allow Change of Language Use Components User Defined Writing Tool Goal Diagrams 6 Information Systems Analysis and Design CSC340 Goal Relationships I I We will use more than AND and OR relationships one goal contributes positively towards the fulfillment of another goal one goal contributes negatively towards the fulfillment of another goal one goal subsumes negates another I e if the first goal is fulfilled the second is fulfilled denied With these enhancements we can build goal models which could be useful for strategic business analysis or requirements analysis 2004 John Mylopoulos Goal Diagrams 7 Information Systems Analysis and Design CSC340 Alternatives for Satisfying Goals I I I I An alternative solution to the fulfillment of a goal G consists of one or more leaf goals which together fulfill the root goal A goal model defines a space of alternatives for the fulfillment of its root goal An alternative A1 is better than A2 in fulfilling goal G with respect to softgoals G 1 G2 if A1 s net contributions to G1 G2 e g positive minus negative contributions is greater than that of A2 In general goals and softgoals can be contradictory Given a set of root goals and softgoals there may not be an optimal solution Simon68 Hence the search for good enough solutions 2004 John Mylopoulos Goal Diagrams 8 Information Systems Analysis and Design CSC340 Building Goal Diagrams I I I I I Start from one or more goals and or softgoals G1 G2 Gn which need to be fulfilled together Analyze each looking for ways to fulfill it through ANDor OR decompositions or through other refinements which contribute positively How questions Continue this process until there is enough positive support to fulfill all root nodes At this point you have n disconnected goal trees T G1 T G2 T Gn Identify positive and negative inter tree influences I e positive or negative relationships between goals g g which belong to different goal trees Repeat the analysis to see if root goals are fulfilled if so done else continue the analysis 2004 John Mylopoulos Goal Diagrams 9 Information Systems Analysis and Design CSC340 Security Maintenability Usability Integrity Availability Accuracy Confidentiality Minimize redundancy Recoverability Extra testing Use Passwords Minimize external communication Do Backups Flexibility 2004 John Mylopoulos Performance Goal Diagrams 10 Information Systems Analysis and Design CSC340 Softgoals as Criteria Quality of schedule Minimal effort Degree of participation Minimal conflicts Matching effort Collection effort Schedule meeting Collect timetables Choose schedule By person By system Manually Automatically By all means By email 2004 John Mylopoulos Have updated timetables Collect them Goal Diagrams 11 Information Systems Analysis and Design CSC340 Library Goals Satisfy every book request Limited loan period Enough copies As many copies as needed Availability notified Regular availability 2004 John Mylopoulos Goal Diagrams 12 Information Systems Analysis and Design CSC340 Public Transit Goals Minimize costs Serve more passengers Trains more closely spaced More tracks Min develop costs Min operating costs Min time between stations 2004 John Mylopoulos Goal Diagrams 13 Information Systems Analysis and Design CSC340 Why Questions Passenger comfort Min operating costs Why do we need smooth movement Smooth movement 2004 John Mylopoulos Goal Diagrams 14 Information Systems Analysis and Design CSC340 Passenger comfort Min operating costs Min equipment stress Min power usage Smooth movement 2004 John Mylopoulos Goal Diagrams 15
View Full Document
Unlocking...