Partial preview of the text
Download Case study harvard university questions study guide. and more Exams Integrated Case Studies in PDF only on Docsity!
Systems Design What is a System? Give examples A scl of components working together for a common objective Information Systems (Web-based) H/w, S/W, people, Data, Procedures. Web-portals What is SLC? Systems Planning. Systems analysis, systems design, systems development, implementation, maintenance IS alignment IS Success IS usage User satisfaction Information waste IS enabled Competitive advantage Orgl change Org! learning TAM Easy to use Percvived personal usefulness Web-based Information System Banner ~ Assess the levels of Flexibility Stakcholders What is Systems Design? Input design Output Design Interface design Database Vechnology — Network architecture, Communications Technology Mlexible Systems Design for Web-based IS? Examples: Banner, Amazon.com, Dell.com — Identify the systems design elements Flexible Systems Design for Web based Information Systems (Research) BOM changes attect MRP In the Banner system, what are the changes that could occur? How do we respond lo these changes? Interviews them Users ~ Students, Registrar (Shanaon), Dean, ete. Designers / Planners - Gary Administration - Lixplore the dimensions — ixtent, Options, cost, easy. Range, etc. Gain more insight by getting more examples. © Application architecture Design * Interface design (User/ System) «Database «Network = Prototype = Systems controls Table 3. Categories of business changes - End-user functions - Precedence among events Capability Maturit Function Point | Whitten et al. Medel Talote (2000) Analysis (2001) Technical requirements [Business requirements [External inputs Functional ~ Performance - Objectives/scope [External outputs —_fequirements -Design constraints Functional requirements {Logical internal files} ~ Inputs - Interface - Business events [External interface | - Outputs requirements - Inputs/outputs files ~ Processes ~ Programming - Relationship between inputs [External inquiries | - Stored data language and outputs \Non-functional System processes transforming system inputs into outputs System backup System recovery - Screens/reports * Source: Low and [requirements Non-technical IExternal interface Jeffery (1990) - Throughput requirements (Operating environment ~ Response time, eae ie - Hardware/software/network pte - Delivery dates Performance requirements ‘iMfiicernes - Response time/throughput ‘Standards requirements - Interface, coding, document l* Source: SEI (1994) Special user Tequirements - Safety, security, reliability - Backup/recovery, transaction) - Training, legal requirements Initial items for business requirements Objectives of the system Interface with other systems System safety System scope Data structure System security Delivery date Data volume Help functions Budget System response time Documentation Business process supported System throughput Legal requirements by the system. System reliability Overall end-user requirements System inputs Transaction types ‘System outputs/reports Transaction volume Case Study: Skills required for Systems Design and Development People skill (25%) - Listening, understanding others, undersianding between two lines, con/lict resolution, handling the communications gaps, reporting, walk through, reviews. Communication Skills (20%) — Oral / Written communication Documentation skills (30%): Knowledge capturing, diagrams, charts (structure charts, Gantt charts, Business knowledge (business processes, business management knowledge) Technical skill (25%) - Database design, programming, web design etc. e What information systems we are talking about... 1. Design of production scheduling and control system (ERP?) 2. Web-based production scheduling and control system 3. Production scheduling and control system e Stake holders for this system 1. Users, oversight committee, Production Manager, Chief Analyst 2. Users, employees, oversight committee, Carla 3. Users, oversight committee, Project Manager (Carla) ¢ Involvement of stakeholders in SDLC Suppliers, Customers, Distributors Financial involvement of stakeholders Users & oversight committee — Systems planning & analysis; Project managers — all phases — involvement through out SDLC. ip © Systems Design activilies 1. Sclect DBMS, Programming Languages, Operating systems, user interface, network design, Architectural design, interface design, network design, database design Hardware & operating systems, web support services, database design, application software design, user interface design 3. Developing database, choosing system software to support web services, determining what changes will be needed to company network Nu Design decisions 1. DBMS selection, application software selection, web support services selection, Ilardware, OS, network changes. ¢ What information systems we are talking about... Web-based production scheduling and control system e Stake holders for this system Users, oversight committee, Production Manager, Chief Analyst, Production & operational employees, Project Manager, top management, consultants, graphic designers, database designers, user interface designers, system interface designers, application developers, network specialists etc. © Involvement of stakcholders in SDLC SDLC phases Users Suppliers, Top Technical (Production | Customers, management | people employees) | Distributors Planning High Medium High Low/Nil Analysis High Medium/Iigh | Medium/Low | Medium/Iligh Design Medium Medium Low High Implementation | Low Low Low/Medium | Tigh © Systems Design activities Design and integrate the network « = New Network/ Existing Network Design the application architecture Specify in details how all system activities will actually be carried out Done in systems analysis in great detail as logical models, without indicating what specific technology Models created include physical data flow diagrams, structure charts, interaction diagrams, and other physical models Design the user interface Defines how the user will interact with the system Graphical user interface with windows, dialog boxes, and mouse interaction. Increasingly, it can include sound, video, and voice commands. Design the system interface (BOM/ MRP) One system provides information that is later used by another system The component that enables systems to share information Design and integrate the database Conceptual, logical, and physical model Relational database consisting of dozens, hundreds, thousands of tables. Prototype design Create and evaluate prototypes Often associated with interface design Used to confirm design choices about the database, network architecture, controls, or even programming environments Design and integrate the system controls Adequate safeguards to protect data/information/ H/w, S/w assets Limit access to the system to authorized users System interface controls cnsure that other systems cause no harm Application controls for recording transactions Database controls - data protection from unauthorized access, accidental loss Network controls - ensure that communication through networks is protected. The outputs of Systems Design Process Application architecture (Process Design) Functionalities/ Business Processes DFD, FDD, Event table, use case etc. Structured Programming Sequential, Conditional, Iterative —3 & 4GL. Network Design Network design document Locations of offices, Servers, LAN/WAN Network capacity (Fig 9-14) Nodes and location diagrams (Fig 9-8) Database Design Conceptual Design Logical Design Physical Design User Interface Design Input forms design Output forms design System Interface Design forms (BOM/ MRP) Design Prototype AGL (Access and Frontpage) Design and Integrate Systems Control User interface- Allow authorized users System Interface- No harms by other systems ((BOM/ MRP) Application architecture — Transaction rules Database architecture- Protect unauthorized access, back-up, recovery Buy options vendor and monitor and monitor Procurement selection, management contracts Outstanding issue control table Issue Title Date Person User Comments Status identified/ | responsible | contact (Done, target date WIP, Not feasible) Partial Jim Jason Ship partials or D shipments wait for full shipment? Return and Jim Bill Are commissions commissions recouped on NF returns? How to handle Extra Mary Bill commissions on | WIP commissions special promotions? Project Schedule (Gantt Chart) Activities/ Gates /Milestones Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Planning Analysis Design Coding Test case development Data Conversion 10 Sequential and Parallel activities (Database design & Network design, status meetings, teleconferencing etc.) Team coordination © Network design team Database design team Application architecture design team User interface design team System interface design team Systems controls design team Prototype design team Team interaction among and between the teams (examples?) Collaborative diagrams for group interactions Common activities for all teams: Status reviews, walk throughs, network configuration, distributed processing, database design, communication capabilities etc. Uncommon activities (Team specific) — Response time for a module, I/O for a module, System interface issues etc. Project team size grows as the system development progresses thru’ SDLC. CASE data repository (Fig 9-6) Knowledge documents - Word, Excel, Visio dgms Dynamically updated Retrieval and referencing Track open items Status walk throughs Open item control log 1 
