100%(2)2 out of 2 people found this document helpful
This preview shows page 1 - 4 out of 29 pages.
Module 1This is a single, concatenated file, suitable for printing or saving as a PDF for offline viewing. Pleasenote that some animations or images may not work.Module 1 Study Guide and DeliverablesReadings:Online lecturesWhitten & Bentley, Primary: pp. 6–16, and 30–33. Secondary: pp. 4–65Discussions:Discussion 1 postings end May 20 at 6:00 AM ETAssignments:Assignment 1 due May 20 at 6:00 AM ETAssessments:Quiz 1 due May 18 at 6:00 AM ETModule 1 ObjectivesThe specific goals of this week's lectures are to define systems analysis: its goals, its processes, and itsparticipants. Systems analysis is sometimes referred to as system analysis (i.e., with no “s”).By reading the lectures and completing the assignments this week, you will be able to:Differentiate between systems engineering, software engineering, and systems analysisDistinguish among types of business systemsRecognize the participants in a systems analysis projectIdentify the contents of systems requirementsDescribe the concept of processIdentify the phases of systems developmentDistinguish between requirements and designUnderstand the importance of the quality assurance processDifferentiate among development process alternativesGrasp the meaning of configuration managementIntroduction
This text will be replaced with: met_cs682_10_fa2_ebraude_w1l1Download()This module’s lectures will introduce systems analysis as a whole. The learning goal for the first lecture is tocover the following topics:Systems Analysis RelationshipsSystem RequirementsTypes of Business SystemsParticipants in Systems AnalysisRelationships Between “Systems Analysis,”“System Engineering” and “SoftwareEngineering”The animationon the rightillustrates thefollowing pointsabout therelationshipsbetweensystemsanalysis,systemengineering,and softwareengineering.In all threefields, weidentifyrequirements:the desired capabilities of the application(s). In all cases, people make the project happen, and they use one ormore processes to achieve this goal.
Systems engineering is distinguished by the integration of hardware and software. Systems analysis isdistinguished by its primary focus on business goals of the future system. In some cases, no programming isneeded if off-the-shelf software can be used to satisfy business goals. Software engineering projects, on theother hand, always involve programming.Real-timecode must execute within hard and fast time constraints. For example, the code that controls theflaps of a jet's wings must respond within a very short time to airplane controls. This is an important aspect ofsystem engineering and software engineering. Databasesare a very common feature of business systems,although they are not restricted to business. Multiple computersare common in systems analysis andsystem engineering (for example, client-server systems). Software engineering typically focuses on developingcomplex software systems that run on one computer at a time (for example, Microsoft Word).