Survey phase objectives - To examine the current problems to be eliminated from the business environment, also the business opportunities - To derived from the user’s business needs a clear set of business objectives for the new system - To define the initial scope of the system and set delimiters around the functional areas to be covered by the project - Identify high level set of business functions that the new system is to support - Identify project constrains, risks and assumptions Activities- Analyze current situation - Define system measurement project business objectives - Create system context diagram - Create data context diagram - Identify project constraints, risks and assumptions - Determine initial project scopeAnalyze the current situation Major type of information to be gathered - Business goals and objectives - Problems and opportunities - High level business processes- Assumptions - Critical success factors - High level information needs - External agents and major business events to which the business areas must react Interviews Basic interview guidelines: before, during, afterNote:- User concentrates on symptoms of problems rather than on real causes all the problems - User expresses needs in terms of predetermined computer solutions with out understanding real nature of the problems.- User may be unfamiliar with what the computerized systems can provide; can make false assumptions- During interview, analyst may notice disparities between official version of business processes and what really happens at the operational level – Use tact and diplomacy when reporting during these to management Questionnaires designObservation analysisProcess flow analysisGroup Brainstorming – informal, focus on idea generation- problem identification, symptoms and causes of problem, opportunities, suggestions to solve a problemPrioritizing problems/opportunities - in order of importance - In terms of ranking categories (Table 2-11)Most common problems/ opportunities - Revised corporate policy, contractual obligations - Government regulations or laws - Technology breakthroughs for competitive advantage - Increase revenues for avoid costs - Enhance existing / support new business services or processes - Reduction of various business operating costs- Shrinking time to market - New system interfaces must be added - Deficiencies in existing system – obsolete technology, High maintenance costs, Throughput limitations, Reliability/ integrity /accuracy problems, Lack of flexibility to support new business processesPrioritization Essential : Requirements without which the user could not properly operate in their business environment Adaptable : requirements that, if need be, can be partly modified to allow alternative modes of operation Nice to have : can be excluded from if they prove too costlySystem mission and project business objectives Mission: are we building the right system?- Why should this system exist - Which business needs and processes does it support - With does this system fit in the overall corporate picture Project business objectives- Provides framework for elaborating the justification But - In relation to problems / opportunities defined- And some objectives may be more important than others- Should be quantifiable and measurable Guidelines in defining business objectivesConciseness – clear and concise, 1-3 sentences.- directed at achieving an end result, not the intermediate steps- Should not try to identify work to be done, rather the desirable end resultMeasurability (Table 2-15)- Reduce inventory costs by 20 percent within two years- Reduce invented costs by $500,000 within one year- And increase ability to handle customer requests on status of their orders from 50 to 75%, within the next year- The reduce elapsed time between receiving a customer order and validating the customer’s credit status by 15%Attainability- attainable in the current organizational context- realistic target date.Strategy for verifying them laterSystem context diagram- Organizational context all the system- Identify high level business processes to be included in the system scope, and those to be excluded - Verify that proposed system is not redundant with respect to other systems in placeWorkflows between system and external entitiesHigh level business processes- Brief narrative description- Business unit(s) responsible, stakeholders.Date that context diagram- High level data entities all the interest, - Relationships amongst the entities and a critical business policies related to these- High level entity-relationship diagram - Indicate entities within and outside system scopeIdentify project constraints, risks and assumptionsDetermine initial project scopeJoint Facilitated