Presentation on theme: "CIS 375 Bruce R. Maxim UM-Dearborn"— Presentation transcript:
1 CIS 375 Bruce R. Maxim UM-Dearborn System EngineeringCIS 375Bruce R. MaximUM-Dearborn
2 Computer System Elements Software.Hardware.People.Databases.Documentation.Procedures (for humans, not code).
3 System Engineering Don't take a "software-centric" view of the system. Consider all system elements before focusing on software.System engineering begins with a clear understanding of the "world view" and progressively narrows until technical detail is understood.Complex systems are actually a hierarchies of subsystems.
4 System Engineering Hierarchy World viewDomain viewElement viewDetailed view
5 Project Engineering Hierarchy Requirements engineeringworld viewComponent engineeringdomain viewAnalysis and Design modelingelement view (software engineers)Construction and Integrationdetailed view (software engineers)
6 Business Process Engineering Hierarchy Information Strategy Planningworld viewBusiness Area Analysisdomain viewBusiness System Designelement view (software engineers)Construction and Integrationdetailed view (software engineers)
7 Business Process Engineering Architectures Data architectureprovides framework for information needs of a business or business functionApplications architecturesystem elements that transform objects within the data architecture for some business purposeTechnology infrastructureprovides foundation for the data and application architectures
8 Computer Systems Engineering Software EngineeringHardware EngineeringHuman Engineering
9 Computer System Analysis Tasks -1 Transform customer defined goals and constraints into system representation describing:Function.Performance.Interfaces.Design constraints.Information structures.
10 Computer System Analysis Tasks -2 Bound the system and select the configuration using:Project schedule and costs.Business considerations.Technical analysis.Manufacturing evaluations.Human issues.Environmental interface.Legal considerations.
11 Human Engineering Activity analysis Semantic analysis and design watch the people you’re supportingSemantic analysis and designwhat and why they do thingsSyntactic and lexical designhw & sw implementation (e.g key strokes)User environment designphysical facilities and HCI stuff
12 Requirements Engineering - 1 Requirements Elicitationfind out from customerwhat the product objectives arewhat is to be donehow the product fits into business needshow the product is used on a day to day basisRequirements Analysisrequirements organized into subsetsrelations among requirements identifiedrequirements reviewed for correctnessrequirements prioritized based on customer needs
13 Requirements Engineering - 2 Requirements Specificationwork product produced describing:functionperformancedevelopment constraints for systemSystem Modelingsystem representation that shows relationships among the system components
14 Requirements Engineering - 3 Requirements Validationexamines the specification to ensure requirement qualitymake sure work products conform to agreed upon standardsRequirements Managementset of activities that help project team to control and track requirements changes as project proceeds
16 System ModelingDefine processes that serve needs of the view under considerationRepresent process behavior and the assumptions on which it is modeledExplicitly define links between constituents and the links between constituent components that are input to the modelRepresent all linkages (including outputs) required to understand the view
17 System Model Restraining Factors AssumptionsSimplificationsLimitationsConstraintsPreferences
18 System Model Template User interface Input Process and control functionsOutputMaintenance and self test
20 Systems Modeling Process - 1 System Context Diagram (SCD or ACD)top level node in system hierarchy used to establish the boundaries for the system being implementedSystem Flow Diagram (SFD or AFD)refinement of the process and control functions from SCDderived by identifying the major subsystems and lines of information flow
21 Systems Modeling Process- 2 Initial SFD is becomes the top level node of a hierarchy of more successively more detailed SFD'sSystem Specificationdeveloped by writing narrative description for each subsystem and definitions for all data that flow between subsystems
22 System SimulationIf simulation capability is not available for a reactive system, project risk increases.Consider using an iterative process model that will allow the delivery and testing of incrementally more complete products.
23 ACD Component Management Engineer Table1.CSV Part Number Table2.CSV INPUTPROCESSINGOUTPUTMAINTENANCE AND SELF-TESTUSER INTERFACE PROCESSINGPROCESS ANDCONTROL FUNCTIONSComponentManagementEngineerDesign ComponentPart Number orValidationMenu SelectionResultTable1.CSVMaster PN and3D Model InfoPart NumberTable2.CSVPrinterAnalysis (PNA) ToolMaster PN andValidationCross-Ref PNResultDataWKConnectors.ErrorCSVMessageDesign ComponentPart NumberComponentManagementEngineer
24 AFD Operator Interface PNA Processing and Control Data Acquisition View/Print ValidationDesign Component PartResultsNumber or Menu SelectionOperatorInterfacesubsystemDisplay GUIPer form AnalysisRequested DataErrorData RequestConnectivity CheckApplicationMessageandStartupInstructionsPart NumbersubsystemAnalysisFormattedsubsystemValidationMS ACCESSResultMS ACCESSData SourceDesign Component PartFormattedPrintingConnectivityNumber, Master PartValidationsubsystemsubsystemNumber, Cross-Ref PartResultNumber and ModelInformationReportFormattingData TablesubsystemManagementDesign Component PartValidationsubsystemNumber, Master PartUnformattedResultPNAProcessingNumber, Cross-Ref PartValidationNumber and ModelResultInformationError CodeError CodeErrorand ControlCodeMS ACCESSError CodeError CodeRun-timeDiagnosticsError CodesubsystemData AcquisitionOutputInterfaceDiagnostic InterfaceInterfaces
25 Data Processing 10 1 2 9 8 3 6 5 7 4 CRITERIA: REPORT10TBL_CREATEDWKCONNWKCONNECTORSVALIDATION DATA- UNIQUE PN- USAGECOMPARISON RESULT12TABLE CRITERIA9QUERYCONSTRUCT SUB-TABLESCOMPARE DATA8365TBL_CREATEDT17TABLE1QUERY RESULTCRITERIA:(1) Do not consider leading zeroes and dashes(2) Consider leading zeroes and dashesTBL_CREATEDT24TABLE2QUERY RESULT
26 Storyboard MULTIPLE PART NUMBER VALIDATION SINGLE PART NUMBER PART NUMBER ANALYSIS TOOLMain(Version / Release Date)(Logo / Branding)Part Number Quick CheckAnalyze Part NumbersView / Print ReportSave ReportExitHelpStatusPlease wait…Data analysis currently in progress.Updated when analysis is finished.StatusData analysis finished.Report has been created.OKPREVIEW REPORT ON SCREEN.Part Number Quick CheckAnalyzeClosePart NumberOutput ToSelect formatOKCancelHTMLMicrosoft ExcelMS-DOS TextRich Text formatSnapshot formatSAVE VALIDATIONDATAResultPart Number***belongs to category X (GOOD/NEW/BAD)Comments:(Place Remarks here)OKMS ACCESS dialog carries out File Save ProcessSINGLE PART NUMBERVALIDATION
27 DFD/CFD Level 0 - Part Number Analysis (PNA) System WKConnectors.XLSSpreadsheet InformationCSV File Creation(WKConnectors.CSV)Display MonitorWKConnectors Delimited TextInformationReport ResultsTable1.CSVPART NUMBER ANALYSIS (PNA) ToolFileTable1 Delimited Text InformationReport ResultsTable2 Delimited Text InformationTable2.CSVReport ResultsPrinter- Command- PN dataUser
28 DFD/CFD Level 1 - Part Number Analysis (PNA) Tool WKConnectors Delimited TextinformationReport ResultsValidation ResultsValidate DataTable1 Delimited TextinformationProcess ReportReport ResultsPrint / SaveDataReport ResultsTable2 Delimited Textinformation- Command- PN data