BIT The thesis is a system work 1 -(14) Thesis seminar The Thesis is a System Work Kirsti Jalasoja
BIT The thesis is a system work 2 -(14) 1 Different types of theses 2 System development models 3 Development methods and description languages 4 development standards
BIT The thesis is a system work 3 -(14) 1 Different types of theses An IT Research A System Development work A Methodology Development work Thesis type Models Documentation An IT Research Research process Research report An IT Strategic Planning IT strategic planning methodology IT strategy report A Feasibility Study development methodology Feasibility study report A System Development work A Requirements engineering development methodology Requirements document A engineering A Data Communication Development development methodology A Dataware Development product / Dataware/ Data communication solutions document
BIT The thesis is a system work 4 -(14) 2 System development models 2.1 Practices and standards of the sponsor/acquirer organization 2.2 A software engineering process de facto 2.3 ISO12207 life cycle processes 2.4 Rational Unified Process (RUP) 2.5 RUP and ISO 12207 2.6 Practices and standards you have used in HAAGA-HELIA 2.7 Other topical methodologies
BIT The thesis is a system work 5 -(14) 2.1 Models and methods of the sponsor/acquirer organization Business domain analysis / system requirements Define services, functionality and other requirements of the system. The customer approves the requirements. requirements analysis Define data structure, functionality, architecture and constraints of the software or software unit according to the system requirements. The customer approves the requirements. design and implementation Produce software (unit) that meets the software requirements. validation Validate the software to ensure that it works according to the specifications and does what the customer wants. evolution Implement you software (unit) so that it evolves changes in customer needs.
BIT The thesis is a system work 6 -(14) 2.2 A software engineering process, de facto Kotonoya&Sommerville: Requirements engineering, Processes and Techniques System requirements engineering System validation Architectural design System integration Requirements partitioning Sub-system development requirements engineering
BIT The thesis is a system work 7 -(14) 2.3 ISO 12207 Standard Life Cycle, version 2 System life cycle processes (not all) Agreement Technical processes (not all) processes Processess Acquisition Process Stakeholder Requirements Definition process Sofware life cycle processes (not all) SW Implementation processes SW Support Processes (not all) Implementation Documentation Management Process Supplier Process System Requirements Analysis Process Requirements Analysis Configuration Management Process System Architectural Design Process Architectural Design Quality Assurance Process System Intergration process System Qualification Testing Process Implementation Process Detailed Design construction Intergration Verification Process Validation Process Installation Process acceptance support Process Operational Process Maintenance Process Qualification Testing
BIT The thesis is a system work 8 -(14) 2.4 Rational Unified Process (RUP) Phases Disciplines Inspection Elaboration Construction Transition Technical disciplines Business modeling Requirements Analysis and design Implementation Test Establish the project s software scope and boundary conditions. Specify the end product vision, preliminary use cases and data storages. Specify the features and design the architecture of the end product. Develop the product and evolve the end product vision, the archicteture and plans Transit the product to its users: - manufacfure - delivery - train - support - maintain until users are satisfied. Deployment Estimate cost and risks. Supporting disciplines Configuration and Change management Track and maintain the integrity of evolving project assets. Management of changes in requirements, design and implementation.. Project management Proved a framework for managing software-intesive projects and risk. Environment Development tool selections and acquitsition and tehnical services Process configuration and improvement
BIT The thesis is a system work 9 -(14) 2.5 Rational Unified Process and ISO 12207 Technical disciplines Inspection Elaboration Construction Transition Business modeling Feasibility Studies Stakeholders Requirements definition Acceptance support Requirements System Requirements Analysis - target state of the business and system requirements analysis Analysis and design System Architectural Design architectural design Sofware detailed design Implementation Implementation Plan Construction plan construction and testing System Intergration Plan Intergration plan Integration and testing Test Deployment System Qualification Testing plan Sofware Installation Deployment Plan Qualification Testing Plan Detailed Deployment Plan System Integration and Qualification Testing Acceptance testing Installation
BIT The thesis is a system work 10 -(14) 2.6 Models, methods and documentation guidelines in HAAGA-HELIA Feasibility study process - coming BUS8TF009 Business Case Selection and Application Selection System requirements engineering - old curriculum SYS8TF060 IS Requirements engineering (myy.haaga-helia.fi/~jalki/sys8tf060) - new curriculum BUS1TF002 Business Process Design and Modelling (myy.haaga-helia.fi/~jalki/bus1tf002) requirements engineering / specification process - old curriculum SYS8TF060 IS Requirements engineering and SYS4TF048 Developing Information System - new curriculum SYS1TF080 Information System Development project design and implementation processes - old curriculum SYS4TF048 Developing Information System - new curriculum SYS1TF080 Information System Development project System testing / validation processes - old curriculum SYS4TF048 System Testing course - new, coming ITP4TF499 QA and Testing
BIT The thesis is a system work 11 -(14) 2.7 Other topical methodologies Prototyping Rapid Application Development (RAD) Incremental delivery methods (like RUP) Agility methods SCRUM - an iterative and incremental process for developing a software - when requirements are rapidly changing - when the development process is unpredictable - interations based on top level system requirements and architecture
BIT The thesis is a system work 12 -(14) 3 Development methods and description languages 3.1 Development methods Analysis methods Environment modelling Business process modelling and reengineering Goal setting Entity-Structure and life cycle analyses Class modelling Automation analysis Data access path analysis Analysis and Design methods (Object-Oriented) Use case modelling Class modelling (business entities/database/software/ interface structure etc.) State machine model (entities/control classes/ mechanisms/operation s methods) Communication modelling component modelling System architectural design and deployment modelling Use of packages
BIT The thesis is a system work 13 -(14) 3.2 Description languages, e.g. Business analysis Business process model - process flow chart - event flow chart - activity diagram of UML Entity-Structure / Class diagram State diagram System analysis, design and implementation Unified Modeling Language (UML 1.4.2 ISO/IEC 19501) Table Text, pseudo code, algorithm Traceability matrix Decision table Programming languages Database management languages
BIT The thesis is a system work 14 -(14) 4 development standards, a few: ISO/IEC 12207 Systems and Sofware engineering - lice cycle processes, 2008 ISO/IEC/TR 15271 Information technology - Guide for ISO/IEC 12207, 1997 (for the standard year 1995) ISO/IEC 6592 Information technology Guidelines for the documentation of computer based application systems, 2000 ISO/IEC 19501 Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2, 2005