Embed Size (px)
DESCRIPTION
Systems analysis. - PowerPoint PPT Presentation
Citation preview
Systems analysis
Systems analysis is the study of systems — sets of interacting entities, including computer systems. This field is closely related to operations research. It is also "an explicit formal inquiry carried out to help someone, referred to as the decision maker, identify a better course of action and make a better decision than he might have otherwise made.
การทำ�า~30% -40%
ขั้��นตอน ขั้��นตอน 22การจั�ดการจั�ดทำ�าทำ�าและและพั�ฒนาพั�ฒนาซอฟต�แซอฟต�แวร�วร�
แนวทำางการบร�หารจั�ดการโครงการทำ��ด� แนวทำางการบร�หารจั�ดการโครงการทำ��ด� (Scope = (Scope = Resources + Time)Resources + Time)
INFORMATIONINFORMATION
Hardware/ Hardware/ Software Of Software Of Computer and Computer and NetworkNetwork
People warePeople ware
BUSINESS RULE BUSINESS RULE / ACTS:- / ACTS:- Structured Structured Rules / Code of Rules / Code of Conducts/ Conducts/ ETHICSETHICS
Digital FirmsDigital Firms ขั้�บขั้�บเคล!�อนห"วงโซ"ค#ณค"าเคล!�อนห"วงโซ"ค#ณค"า 11
Software Back Software Back Bone Bone ขั้�บเคล!�อนห"วงขั้�บเคล!�อนห"วงโซ"ค#ณค"า โซ"ค#ณค"า 22
กระบวนงานกระบวนงานICTICTขั้�บขั้�บเคล!�อนห"วงโซ"ค#ณค"า เคล!�อนห"วงโซ"ค#ณค"า 33
ก�าหนดกรอบ ก�าหนดกรอบ เวลาเวลา…….>.>
BUDGETS
แกนต��งการสร&างความแกนต��งการสร&างความพัร&อม จั�ดสรรทำร�พัยารทำ��พัร&อม จั�ดสรรทำร�พัยารทำ��จั�าก�ดขั้องโครงการ จั�าก�ดขั้องโครงการ CSF CSF of ICT of ICT Infrastructure Infrastructure (CBIS/ TBIS) (CBIS/ TBIS) ค!อค!อ>>>>
บรรล#แผนบรรล#แผนICT ICT ขั้�บเคล!�อนขั้�บเคล!�อนห"วงโซ"ค#ณค"า ห"วงโซ"ค#ณค"า 4 4 ส"งเสร�ม ส"งเสร�ม สน�บสน#น และผล�กด�นการสน�บสน#น และผล�กด�นการบร�หารจั�ดการทำ��ด� ตามแผนบร�หารจั�ดการทำ��ด� ตามแผนแม"บทำ แม"บทำ ICT / SISPICT / SISP
การแก&ไขั้ ปิ,ดโครงการ~~--30% -10%30% -10%ขั้��นตอน 3การทำดสอบและปิร�ปิระบบ ฝึ.กอบรมใช้&งาน และจั�ดการศู2นย�ขั้&อม2ล.เพั!�อ MA
การค�ด ~40% -50% ขั้��นตอน ขั้��นตอน 11การการศึ�กษาศึ�กษาวิ�เคราะห์�วิ�เคราะห์�และออกและออกแบบเป้�า แบบเป้�า ป้ระสงค�ป้ระสงค�กระบวินกระบวินงานและงานและขั้�อมู�ลขั้�อมู�ล
ทำบทำบทำวทำวนน
ทำบทำวน
ทำบทำบทำวทำวนน
ทำทำบบทำวทำวนน
ขั้อบเขั้ต การขั้อบเขั้ต การบร�หารบร�หาร
โครงการไอทำ�โครงการไอทำ�ทำ��ด�ทำ��ด�
•GoalsGoalsArchitectureArchitecture
•BusinessBusinessProcessProcessArchitectureArchitecture
•DataDataArchitectureArchitecture
•ApplicationApplicationArchitectureArchitecture
•ICTICT InfrastructureInfrastructureArchitectureArchitecture•ICTICTGood GovernanceGood GovernanceArchitectureArchitecture
ออกแบบ
Types of Types of Systems Systems analysis analysis
Related Related topics topics
Systems Systems thinkersthinkers
Accident Analysis Cybernetics Gregory Bateson
Business analysis Process architecture
Stewart Brand
Morphological analysis
Program designer
Buckminster Fuller Software prototypi
ngSystems analyst
Robert S. McNamara Spiral model Systems desi
gn
Stafford Beer
Waterfall model Systems thinking
Gordon Pask
Policy analysis
Ludwig von Bertalanffy
1. Business analysis 2. Enterprise Architecture Planning 3. Enterprise modeling 4. Product lifecycle management 5. Service-oriented modeling life cycle 6. Software Lifecycle Processes 7. Systems Development Life Cycle 8. Technology Life Cycle 9. Whole-life cost
Accident Analysis is carried out in order to determine the cause or causes of an accident or series of accidents so as prevent further incidents of a similar kind. It is also known as accident investigation. It may be performed by a range of experts, including forensic scientists, forensic engineers
SequenceAccident Analysis is performed in four steps:
1. Fact gathering After an accident happened a forensic process starts to gather all possibly relevant facts that may contribute to understanding the accident.
2. Fact Analysis After the forensic process has been completed or at least delivered some results the facts are put together to give a "big picture." The history of the accident is reconstructed and checked for consistency and plausibility.
3. Conclusion Drawing If the accident history is sufficiently informative conclusions can be drawn about causation and contributing factors.
4. Countermeasures In some cases the development of countermeasures is desired or recommendations have to be issued to prevent further accidents of the same kind.
MethodsMethodsThere exist numerous forms of Accident Analysis methods. These can be divided into There exist numerous forms of Accident Analysis methods. These can be divided into
three categories (in alphabetical order)three categories (in alphabetical order)
1.1. Causal AnalysisCausal Analysis uses the principle of causality to determine the course of uses the principle of causality to determine the course of eventsevents. . Though people casually speak of a Though people casually speak of a ""chain of eventschain of events" " results from Causal results from Causal Analysis usually have the form of directed aAnalysis usually have the form of directed a--cyclic graphscyclic graphs. . The nodes being The nodes being events and the edges the causeevents and the edges the cause--effect relationseffect relations. . Methods of Causal Analysis Methods of Causal Analysis differ in their respective notion of causationdiffer in their respective notion of causation. .
2.2. Expert AnalysisExpert Analysis relies on the knowledge and experience of field experts. This for relies on the knowledge and experience of field experts. This form of analysis usually lacks a rigorous (formal/semiformal) methodological approm of analysis usually lacks a rigorous (formal/semiformal) methodological approach. This usually affects falsify-ability and objectivity of analyses. This is of impach. This usually affects falsify-ability and objectivity of analyses. This is of importance when conclusions are heavily disputed among experts. ortance when conclusions are heavily disputed among experts.
3.3. Organisational AnalysisOrganisational Analysis relies on systemic theories of organisation relies on systemic theories of organisation. . Most Most theories imply that if a systems behaviour stayed within the bounds of the ideal theories imply that if a systems behaviour stayed within the bounds of the ideal organisation then no accidents can occurorganisation then no accidents can occur. . Organisational Analysis can be Organisational Analysis can be falsified and results from analyses can be checked for objectivityfalsified and results from analyses can be checked for objectivity. . Choosing an Choosing an organisational theory for accident analysis comes implies the assumption that organisational theory for accident analysis comes implies the assumption that the system to be analysed conforms to that theorythe system to be analysed conforms to that theory. .
Business analysisBusiness analysisFrom Wikipedia, the free encyclopediaFrom Wikipedia, the free encyclopediaJump toJump to::navigation, , search Business analysisBusiness analysis is the is the discipline[1] of identifying business needs and of identifying business needs and determining solutions to business problemsdetermining solutions to business problems. . Solutions often include a systems Solutions often include a systems development component, but may also consist of process improvement or development component, but may also consist of process improvement or organizational change or strategic planning and policy developmentorganizational change or strategic planning and policy development. . The The person who carries out this task is called a person who carries out this task is called a business analyst or BA or BA. . [2]Those BAs who work solely on developing software systems may be called IT Those BAs who work solely on developing software systems may be called IT Business Analysts, Technical Business Analysts, or Systems Analysts.Business Analysts, Technical Business Analysts, or Systems Analysts.ContentsContents[[hidehide]]Business analysis subBusiness analysis sub--disciplinesdisciplinesBusiness analysis as a discipline has a heavy overlap with Business analysis as a discipline has a heavy overlap with requirements analysis sometimes also called requirements engineering, but sometimes also called requirements engineering, but focuses on identifying the changes to an organization that are required for it to focuses on identifying the changes to an organization that are required for it to achieve strategic goalsachieve strategic goals. . These changes include changes to strategies, These changes include changes to strategies, structures, policies, processes, and information systemsstructures, policies, processes, and information systems..Examples of business analysis includeExamples of business analysis include::Enterprise analysis or company analysis Enterprise analysis or company analysis
focuses on understanding the needs of the business as a whole, its stratefocuses on understanding the needs of the business as a whole, its strategic direction, and identifying initiatives that will allow a business to meet thgic direction, and identifying initiatives that will allow a business to meet those strategic goals. ose strategic goals.
Requirements planning and management Requirements planning and management involves planning the requirements development process, determining which involves planning the requirements development process, determining which requirements are the highest priority for implementation, and managing chanrequirements are the highest priority for implementation, and managing change. ge.
Requirements elicitation Requirements elicitation describes techniques for collecting requirements from stakeholders in a projdescribes techniques for collecting requirements from stakeholders in a project. ect.
Requirements analysis Requirements analysis describes how to develop and specify requirements in enough detail to allow describes how to develop and specify requirements in enough detail to allow them to be successfully implemented by a project team. them to be successfully implemented by a project team.
Requirements communication Requirements communication describes techniques for ensuring that stakeholders have a shared understandescribes techniques for ensuring that stakeholders have a shared understanding of the requirements and how they will be implemented. ding of the requirements and how they will be implemented.
Solution assessment and validation Solution assessment and validation describes how the business analyst can verify the correctness of a proposed describes how the business analyst can verify the correctness of a proposed solution, how to support the implementation of a solution, and how to assess solution, how to support the implementation of a solution, and how to assess possible shortcomings in the implementation. possible shortcomings in the implementation.
Business analysis techniquesBusiness analysis techniquesThere are a number of techniques that a Business Analyst will use when There are a number of techniques that a Business Analyst will use when facilitating business changefacilitating business change. . These range from workshop facilitation techniques These range from workshop facilitation techniques used to elicit requirements, to techniques for analysing and organising used to elicit requirements, to techniques for analysing and organising requirementsrequirements..
Some of these techniques include:PESTLE This is used to perform an external environmental analysis by examining the many different external factors affecting an organisation.The six attributes of PESTLE:
Political (Current and potential influences from political pressures) Economic (The local, national and world economy impact) Sociological (The ways in which a society can affect an organisation) Technological (The effect of new and emerging technology) Legal (The effect of national and world legislation) Environmental (The local, national and world environmental issues)
MOST This is used to perform an internal environmental analysis by defining the attributes of MOST to ensure that the project you are working on is aligned to each of the 4 attributes.The four attributes of MOST[3]
Mission (where the business intends to go) Objectives (the key goals which will help achieve the mission) Strategies (options for moving forward) Tactics (how strategies are put into action)
SWOT This is used to help focus activities into areas of strength and where the greatest opportunities lie. This is used to identify the dangers that take the form of weaknesses and both internal and external threats.The four attributes of SWOT:
Strengths - What are the advantages? What is currently done well? (e.g Key area of Best Perfoming activites of your company) Weaknesses - What could be improved? What is done badly? (e.g Key area where you are performing bad) Opportunities - What good opportunities face the organisation? (e.g Key area where your competitors are performing bad ) Threats - What obstacles does the organisation face? (e.g Key area where your competitor will performing good)
CATWOE This is used to prompt thinking about what the business is trying to achieve. Business Perspectives help the Business Analyst to consider the impact of any proposed solution on the people involved.There are six elements of CATWOE[4]
Customers - Who are the beneficiaries of the highest level business process and how does the issue affect them? Actors - Who is involved in the situation, who will be involved in implementing solutions and what will impact their success? Transformation Process - What processes or systems are affected by the issue? World View - What is the big picture and what are the wider impacts of the issue? Owner - Who owns the process or situation being investigated and what role will they play in the solution? Environmental Constraints - What are the constraints and limitations that will impact the solution and its success?
De Bono 6Hat This is often used in a brainstorming session to generate and analyse ideas and options. It is useful to encourage specific types of thinking and can be a convenient and symbolic way to request someone to “switch gear. It involves restricting the group to only thinking in specific ways - giving ideas & analysis in the “mood” of the time. Also known as the Six Thinking Hats.
White: Pure, facts, logical. Green: Creative, emotional Yellow: Bright, optimistic, positive. Black: Negative, devil’s advocate. Red: Emotional. Blue: Cold, control.
Not all colours / moods have to be usedFive Why's Five Whys is used to get to the root of what is really happening in a single instance. For each answer given a further 'why' is asked.MoSCoW This is used to prioritise requirements by allocating an appropriate priority, gauging it against the validity of the requirement itself and its priority against other requirements.
MoSCoW comprises:Must have - or else delivery will be a failure Should have - otherwise will have to adopt a workaround Could have - to increase delivery satisfaction Would like to have in the future - but won't have now
VPEC-T Main article: VPEC-TThis technique is used when analyzing the expectations of multiple parties having different views of a system in which they all have an interest in common, but have different priorities and different responsibilities.
Values - constitute the objectives, beliefs and concerns of all parties participating. They may be financial, social, tangible and intangible Policies - constraints that govern what may be done and the manner in which it may be done Events - real-world proceedings that stimulate activity Content - the meaningful portion of the documents, conversations, messages, etc. that are produced and used by all aspects of business activity Trust - trusting (or otherwise) relationship between all parties engaged in a value system
Roles of Business AnalystsAs the scope of business analysis is very wide, there has been a tendency for business analysts to specialize in one of the three sets of activities which constitute the scope of business analysis.Strategist
Organizations need to focus on strategic matters on a more or less continuous basis in the modern business world. Business analysts, serving this need, are well-versed in analyzing the strategic profile of the organization and its environment, advising senior management on suitable policies, and the effects of policy decisions.
Architect Organizations may need to introduce change to solve business problems which may have been identified by the strategic analysis, referred to above. Business analysts contribute by analyzing objectives, processes and resources, and suggesting ways by which re-design (BPR), or improvements (BPI) could be made. Particular skills of this type of analyst are "soft skills", such as knowledge of the business, requirements engineering, stakeholder analysis, and some "hard skills", such as business process modeling. Although the role requires an awareness of technology and its uses, it is not an IT-focused role.
Three elements are essential to this aspect of the business analysis effort: the redesign of core business processes; the application of enabling technologies to support the new core processes; and the management of . This aspect of business analysis is also called "business process improvement" (BPI), or "reengineering".
Systems analyst There is the need to align IT Development with the systems actually running in production for the Business. A long-standing problem in business is how to get the best return from IT investments, which are generally very expensive and of critical, often strategic, importance. IT departments, aware of the problem, often create a business analyst role to better understand, and define the requirements for their IT systems. Although there may be some overlap with the developer and testing roles, the focus is always on the IT part of the change process, and generally, this type of business analyst gets involved, only when a case for change has already been made and decided upon.
In any case, the term "analyst" is lately considered somewhat misleading, insofar as analysts (i.e. problem investigators) also do design work (solution definers).
Business process improvementA business process improvement (BPI) typically involves six steps:(reference? - basis required)1. Selection of process teams and leaderProcess teams, comprising 2-4 employees from various departments that are involved in the particular process, are set up. Each team selects a process team leader, typically the person who is responsible for running the respective process.2. Process analysis trainingThe selected process team members are trained in process analysis and documentation techniques.3. Process analysis interviewThe members of the process teams conduct several interviews with people working along the processes. During the interview, they gather information about process structure, as well as process performance data.4. Process documentationThe interview results are used to draw a first process map. Previously existing process descriptions are reviewed and integrated, wherever possible. Possible process improvements, discussed during the interview, are integrated into the process maps.
5. Review cycleThe draft documentation is then reviewed by the employees working in the process. Additional review cycles may be necessary in order to achieve a common view (mental image) of the process with all concerned employees. This stage is an iterative process.6. Problem analysisA thorough analysis of process problems can then be conducted, based on the process map, and information gathered about the process. At this time of the project, process goal information from the strategy audit is available as well, and is used to derive measures for process improvement.Goal of business analystsUltimately, business analysts want to achieve the following outcomes:One way to assess these goals is to measure the return on investment (ROI) for all projects. Keeping score is part of human nature as we are always comparing ourselves or our performance to others, no matter what we are doing. According to Forrester Research, more than $100 billion is spent annually in the U.S. on custom and internally developed software projects. For all of these software development projects, keeping score is also important and business leaders are constantly asking for the return or ROI on a proposed project or at the conclusion of an active project. However, asking for the ROI without really understanding the underpinnings of where value is created or destroyed is putting the cart before the horse.
[edit] Reduce waste and complete projects on timeProject delays are costly in three different dimensions:N.B. On a lot of projects (particularly larger ones) the project manager is the one tasked with ensuring that a project is completed on time. The BA's job is more to ensure that if a project is not completed on time then at least the highest priority requirements are met.See also: Cancelled projects[edit] Document the right requirementsBusiness analysts want to make sure that they define the application in a way that meets the end-users’ needs. Essentially, they want to define the right application. This means that they must document the right requirements through listening carefully to ‘customer’ feedback, and by delivering a complete set of clear requirements to the technical architects and coders who will write the program. If a business analyst has limited tools or skills to help him elicit the right requirements, then the chances are fairly high that he will end up documenting requirements that will not be used or that will need to be re-written – resulting in rework as discussed above. The time wasted to document unnecessary requirements not only impacts the business analyst, it also impacts the rest of the development cycle. Coders need to generate application code to perform these unnecessary requirements and testers need to make sure that the wanted features actually work as documented and coded. Experts estimate that 10% to 40% of the features in new software applications are unnecessary or go unused.
Being able to reduce the amount of these extra features by even one-third can result in significant savings.[edit] Improve project efficiencyEfficiency can be achieved in two ways: by reducing rework and by shortening project length.Rework is a common industry headache and it has become so common at many organizations that it is often built into project budgets and time lines. It generally refers to extra work needed in a project to fix errors due to incomplete or missing requirements and can impact the entire software development process from definition to coding and testing. The need for rework can be reduced by ensuring that the requirements gathering and definition processes are thorough and by ensuring that the business and technical members of a project are involved in these processes from an early stage.Shortening project length presents two potential benefits. For every month that a project can be shortened, project resource costs can be diverted to other projects. This can lead to savings on the current project and lead to earlier start times of future projects (thus increasing revenue potential).
Enterprise Architecture Process
Architecture Life Cycle
Enterprise Life Cycle Activities
Enterprise Performance Lifecycle
The Zachman Framework is an Enterprise Architecture
The Zachman Framework is an Enterprise Architecture DETAIL
The Zachman Framework is an Enterprise Architecture DETAIL
Enterprise Architecture Planning
Enterprise Modelling
Business Process Modelling
Government Business Reference
Enterprise Integration
Enterprise ENTITY Concept
Enterprise Engineer for Life Cycle
ISO 19439:2006 Enterprise integration -- Framework for enterprise modelling,
Enterprise Evolution
Semantic Data Models
Enterprise Architecture framework Patterns in Enterprise Architecture Domains
Enterprise Architecture Model
