1 / 80

The Systems Design

The Systems Design. By Daniel Damaris Novarianto S. LOGO. Develop IT System. Develop IT Systems. Why the companies develop the IT system? IT support their current and future business operations IT needs are immediate, such us fixing a logic problem in a payroll system

tmoss
Download Presentation

The Systems 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. The Systems Design By Daniel Damaris Novarianto S. LOGO

  2. Develop IT System

  3. Develop IT Systems • Why the companies develop the IT system? • IT support their current and future businessoperations • IT needs are immediate, such us fixing a logic problem in a payroll system • IT support for a new factory, a future merger, or a corporate restructuring • IT team reviews each IT-related proposal, project, and systems request to determine if it presents a strong business case or justification

  4. Strategic Planning for IT Case

  5. Main Reasons of Systems Projects

  6. Factors that Affect Systems Projects

  7. Who is Develop and Maintain the IT System in Companies?

  8. Who is Develop & Maintain the IT System in Companies?

  9. IT Department • Application Development • The Application system are developed by team consisting of users, manager, and IT staff manager • System Support & Security • This group implements and monitors physical and electronic security hardware, software, and procedures • Installs and supports operating systems, telecommunications software, and centralized database management systems

  10. IT Department (cont.) • User Support • This group usually is called a help desk or information center (IC) • A help desk’s staff trains users and managers on application software such as e-mail, word processing spreadsheets, and graphics packages • User support specialists answer questions, troubleshoot problems, and serve as a clearinghouse for user problems and solutions

  11. IT Department (cont.) • Database Administration • This group usually involves data design, management, security, backup, and access • In small- and medium-sized companies, an IT support person performs those roles in addition to other duties • Regardless of company size, mission-critical database applications require continuous attention and technical support

  12. IT Department (cont.) • Network Administration • They are controlling user access, network administrators install, configure, manage, monitor, and maintain network applications • Includes hardware and software maintenance,support, and security

  13. IT Department (cont.) • Web Support • Web support specialists design and construct Web pages, monitor traffic, manage hardware and software, and link Web-based applications to the company’s information systems

  14. IT Department (cont.) • Quality Assurance (QA) • This team reviews and tests all applications and systems changes to verify specifications and software quality standards • The QA team usually is a separate unit that reports directly to IT management

  15. The System Analysis

  16. Modeling Tools & Techniques • Functional Decomposition Diagrams (FDD) • Business Process Modeling (BPM) • Data Flow Diagram (DFD) • Unified Modeling Language (UML)

  17. The Functional Decomposition Diagram (FDD) • A top down representation of a function or process • Using an FDD, an analyst can show business functions and break them down into lower-level functions and processes • Creating an FDD is similar to drawing an organization chart

  18. The Example of FDD (Library)

  19. The Business Process Modeling (BPM) • A (BPM) describes one or more business processes, such as handling an airline reservation, filling a product order, or updating a customer account • During requirements modeling, analysts often create models that use a standard language called business process modeling notation (BPMN) • Including various shapes and symbols to represent events, processes, and workflows

  20. The Example of BPM

  21. The Data Flow Diagram (DFD) • The DFD show how the system stores, processes, and transforms data

  22. The Example of DFD (Online Store)

  23. The Unified Modeling Language (UML) • This method widely used to visualizing and documenting software systems design • UML provides various graphical tools, such as: • Use Case Diagrams and • Sequence Diagrams

  24. The UML (cont.) • Use Case Diagram • A use case diagram visually represents the interaction between users and the informationsystem. • In a use case diagram, the user becomes an actor, with a specific role that describes how he or she interacts with the system • Systems analysts can draw use case diagrams freehand or use CASE tools that integrate the use cases into the overall system design

  25. The UML (cont.) • Sequence Diagram • A sequence diagram shows the timing of interactions between objects as they occur. • A systems analyst might use a sequence diagram to show all possible outcomes, or focus on a single scenario

  26. The Example of Use Case Diagram (Calculator)

  27. The Example of Sequence Diagram

  28. Future Growth, Costs & Benefits • Scalability • A system’s ability to handle increased business volume and transactions in the future • To evaluate scalability, you need information about projected future volume for all outputs, inputs, and processes. • You need to determine how much data storage is required currently and predict future needs based on system activity and growth

  29. Future Growth, Costs & Benefits (cont.) • Total Costs of Ownership • A systems developers must identify and document indirect expenses that contribute to the total cost of ownership (TCO) • One problem is that cost estimates tend to understate indirect costs such as user support and downtime productivity losses • E.g: Microsoft developed Rapid Economic Justification (REJ) to analyze and optimize IT investments.

  30. Designing the User Interface

  31. Designing the User Interface • Good user interface design is based on a combination of • Ergonomics describes how people work, learn, and interact with computers • Aesthetics focuses on how an interface can be made attractive and easy to use • Interface Technology provides the operational structure required to carry out the design objectives

  32. Designing the User Interface (cont.) • Design a transparent interface • Create an interface that is easy to learn and use • Enhance user productivity • Make it easy for users to obtain help or correct errors • Minimize input data problems • Provide feedback to users • Create an attractive layout and design • Use familiar terms and images

  33. Designing the User Interface (cont.) • Designing a Transparent Interface • Facilitate the system design objectives, rather than calling attention to the interface. • Create a design that is easy to learn and remember. • Design the interface to improve user efficiency and productivity. • Write commands, actions, and system responses that are consistent and predictable. • Minimize data entry problems. • Allow users to correct errors easily. • Create a logical and attractive layout

  34. Designing the User Interface (cont.) • Create an interface that is easy to learn and use • Clearly label all controls, buttons, and icons • Select only those images that users can understand easily, and provide on-screen instructions that are logical, concise, and clear • Show all commands in a list of menu items, but dim any commands that are not currently available. • Make it easy to navigate or return to any level in the menu structure

  35. Designing the User Interface (cont.) • Enhance User Productivity • Organize tasks, commands, and functions in groups that resemble actual business operations • Create alphabetical menu lists or place the selections used frequently at the top of the menu list • Provide shortcuts so experienced users can avoid multiple menu levels • Use default values if the majority of values in a field are the same. For example, if 90% of the firm’s customers live in Albuquerque, use Albuquerque as the default value in the City field.

  36. Designing the User Interface (cont.) • Enhance User Productivity (cont.) • Use a duplicate value function that enables users to insert the value from the same field in the previous record • Provide a fast-find feature that displays a list of possible values as soon as users enter the first few letters • Use a natural language feature that allows users to type commands or requests in normal English phrases. For example, many applications allow users to request Help by typing a question into a dialog box

  37. Designing the User Interface (cont.) • Make It Easy for Users to Obtain Help or Correct Errors • Ensure that help is always available. Help screens should provide information aboutmenu choices, procedures, shortcuts, and errors • Provide user-selected help and context-sensitive help. User-selected help displays information when the user requests it. Context-sensitive help offers assistance for the task in progress • Provide a direct route for users to return to the point from where help was requested

  38. Designing the User Interface (cont.) • Make It Easy for Users to Obtain Help or Correct Errors (cont.) • Include contact information, such as a telephone extension or e-mail address if a department or help desk is responsible for assisting users • Require user confirmation before data deletion (Are you sure?) and provide a method of recovering data that is deleted inadvertently • Provide an Undo key or a menu choice that allows the user to eradicate the results of the most recentcommand or action

  39. Designing the User Interface (cont.) • Make It Easy for Users to Obtain Help or Correct Errors (cont.) • When a user-entered command contains an error, highlight the erroneous part and allow the user to make the correction without retyping the entire command • Use hypertext links to assist users as they navigate through help topics

  40. Designing the User Interface (cont.) • Minimize Input Data Problems • Create input masks, which are templates or patterns that make it easier for users to enter data. Also use data validation rules, which limit the acceptable values that users can enter • Display event-driven messages and reminders • Establish a list of predefined values that users can click to select • Build in rules that enforce data integrity. For example, if the user tries to enter an order for a new customer, the customer must be added before the system will accept the order data

  41. Designing the User Interface (cont.) • Provide Feedback to Users • Display messages at a logical place on the screen, and be consistent • Alert users to lengthy processing times or delays • Allow messages to remain on the screen long enough for users to read them • Let the user know whether the task or operation was successful or not

  42. Designing the User Interface (cont.) • Provide Feedback to Users • Provide a text explanation if you use an icon or image on a control button • Use messages that are specific, understandable, and professional. Avoid messages that are cute, cryptic, or vague, such as: ERROR — You have entered an unacceptable value, or Error DE4-16

  43. Designing the User Interface (cont.) • Create an Attractive Layout and Design • Use appropriate colors to highlight different areas of the screen; avoid gaudy and bright colors. • Use special effects sparingly • Use hyperlinks that allow users to jump to related topics. • Group related objects and information • Screen density is important. Keep screen displays uncluttered, with enough white space to create an attractive, readable design

  44. Designing the User Interface (cont.) • Create an Attractive Layout and Design (cont.) • Display titles, messages, and instructions in a consistent manner and in the same general locations on all screens • Use consistent terminology. For example, do not use the terms delete, cancel, and erase to indicate the same action • Ensure that commands always will have the same effect

  45. Designing the User Interface (cont.) • Create an Attractive Layout and Design (cont.) • Ensure that similar mouse actions will produce the same results throughout the application • When the user enters data that completely fills the field, do not move automatically to the next field

  46. Designing the User Interface (cont.) • Use Familiar Terms and Images • Remember that users are accustomed to a pattern of red = stop, yellow = caution, and green = go. • Provide a keystroke alternative for each menu command, with easy-to-remember letters, such as File, Exit, and Help • Use familiar commands if possible, such as Cut, Copy, and Paste

  47. Designing the User Interface (cont.) • Use Familiar Terms and Images (cont.) • Provide a Windows look and feel in your interface design if users are familiar with Windows-based applications • Avoid complex terms and technical jargon; instead, select terms that come from everyday business processes and the vocabulary of a typical user

  48. Output Design

  49. Output Design • Before designing output, ask yourself several questions: • What is the purpose of the output? • Who wants the information, why is it needed, and how will it be used? • What specific information will be included? • Will the output be printed, viewed on-screen, or both? What type of device will the output go to? • When will the information be provided, and how often must it be updated? • Do security or confidentiality issues exist?

  50. Output Design (cont.) • Type of Reports • User Involvement in Report Design • Report Design Principle • Output Technology

More Related