1 / 23

Wellcome to learn the fundamentals in Systems Analysis and Design

Wellcome to learn the fundamentals in Systems Analysis and Design. Overview of the course. The course consists of three different parts Theory, which is followed by a written exam. Case study consisting of : Assignments (3 pcs) which will give you bonus for the written exam.

benson
Download Presentation

Wellcome to learn the fundamentals in Systems Analysis and Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wellcome to learn the fundamentals in Systems Analysis and Design

  2. Overview of the course The course consists of three different parts • Theory, which is followed by a written exam. • Case study consisting of : Assignments (3 pcs) which will give you bonus for the written exam. Implementation in MS Access of the case study 3. Selfstudies of MS Access.

  3. Assignments – Bonus pointsExamination • For each assignment, you can get max 5 bonus points. Total 15 points for all assignments (see separate paper for grades). • To qualify for bonus points, each assignment must be handed in before the dead-line for each assignment.

  4. Course material • All course material can be found in BlackBoard • In BB you can also find some sample databases to get some ideas for the implementation

  5. Remember! • Do not forget to study your textbook and/or these OH-slides for each assignment. • Download software from internet. www.pacestar.com has a software called Edge Diagrammer., which is easy to use as a ”drawing software”. • Also download the extensionpacks available for Edge Diagrammer.

  6. Kom ihåg forts. • Edge Diagrammer has a trial period for 30 days • All pictures created with Edge Diagrammer must be pasted into MS Word, to form a report. • Of course, you are free to use any drawing software. There are lots on the market. Like Visio, SmartDraw, ABC-flowchart etc.

  7. Models Many things in Systems Analysis and Design are decribed as models. The reason for this is obvious if you look at this model of an aircraft Try to describe the model of the aircraft with words only……… Conclusion: A drawing software is necessary to use. .

  8. Information system The business Computer system Overview

  9. What a Systems Analysts needs to know • What shall be done • Which tasks must be resolved • How shall it be done • different techniques and methods to solve the task The basic tasks for a Systems Analysts is to present a ”drawing” of the system to be developed (compare with the architect drawing a house).

  10. How do you organize an information systems development? • A sequence of steps, often arranged in time. • A description of these steps constitutes a Systems Development Model. • Specify what shall be done • The models often have references to methods for the work.

  11. Business Analysis(from a Systems Analysts point of view) • Carefully analyse the business/business area in focus Purpose: • to find the business requirements • find urgent requirements/problems • evaluate the requirements/problems • Understand possible changes

  12. Methods • The methods you usually use in this context : • Interviews • Observations • Questionnaire • The most common method is interviews! (in your case study, the interviews is replaced by your carefully analysis of the case study, and…. questions to the teacher)

  13. Feasibility study • A well-researched and well-written feasibility study is critical when making "Go/No Go" decisions regarding entry into new businesses

  14. Document the analysis • A structured documentation of the requirements is easier to understand than having it in continuous text. • Continuous text has the disadvantage that it can be difficult to sort out what are problems, requirements, essentials, unessentials etc.

  15. Problem/ requirement Cause Consequence Proposal Difficult to find info In the files The file contains cards of paper Searching takes a lot of time Computer support for searching Same info is written several times Paper cards Extra work Computer support to enter info into the system Some contractors does not return their keys and other stuff No one checks when to return different documents Costs for stamps to claim . Keys must be produced Computer support to follow up when a contractor is supposed to leave work The card readers are often broken Technical error The door cannot be opened. Guards must be called The problem is handed over to Service department for processing Structured documentation

  16. Another example

  17. Priority • The analysis of the requirements will often show a lot of problems and needs from different areas. • Some kind of priority is needed, because you cannot build a system covering everything. • It is important to focus on the most urgent/most profitable requirements/needs.

  18. Priority • A leading star to follow is that the system should give support to those areas where you find the biggest profit. • These areas are often those supporting the actual Business model. What is the main purpose of the business. (example: a real estate broker has as main purpose to sell houses and real estates)

  19. Priority • Whats is the main purpose of a business? • A car dealer has his/hers main task to sell cars • A real estate broker shall try to connect sellers and byers of houses/real estates. • Etc.

  20. Set goals for a new system • Adter prioritising the requirements/needs, the goals must be set for the new system. • Try to set the goals as concrete as possible. Best is that you have goals that can be measured. • Concentrate on the goals showing what the new system should be able to perform and the effects of the goals.

  21. Setting goals cont. • Examples of setting goals Bad goal: ”The system result in less costs” Good goal: ”The system result in reduced costs from X sek to Y sek”

  22. Setting goals cont. Bad goal: ”The system result in reduced credit time for the customers” Good goal: ”The system result in reduced credit time from X days to Y days”

  23. Setting goals cont.(Example from earlier case study)These goals give good support for the development of the system! Goals for the new system The system shall be able to handle forms and reports supporting following business functions: - Enter info about new contracts - Show/change info about contracts - Print reports for order value/time period, commissions/time period, order value/time period and Salesman/Agent - Show forms for contracts with choosen order value and time period - Enter/Change info about agents and salesmen belonging to agent - Enter/Change info about pricelists for phone calls - Enter/Change info about quantity commissionsfor agents

More Related