Simon Fraser University

• CMPT 276

• 1) Intro to Software Engineering (SE) • Know what is software engineering: person who researches, designs, dev and maintains SW , and the importance of software. • Know the four fundamental software process activities. 1. Specification: features/ constraints of SW 2. Development: design and program the SW 3. Validation/ Testing: SW is up to customer spec (quality) 4. Evolution/ Maintenance: modify SW to reflect change req/ bugs (60% of cost) • Understand each of the four essential attributes of good software. 1. Maintainability: be able to make changes easily 2. Dependability and Security: reliable/ secure/ safe 3. Efficiency: good use of resources (time/space) 4. Acceptability: understandable (user pt. of view) • Compare and contrast generic software and custom software. Generic SW Custom SW - stand alone sys marketed to general public - sys dev. for particular customer to meet their needs • software engineering diversity: make use of existing resources • Understand each type of SW. - Stand Alone Applications - interactive transaction-based app - embedded control sys - entertainment sys - batch processing sys - modelling and sim sys - data collection sys - sys of sys • Webb apps - Saas (software as a service): can be dl from web browser 2) Ethics and Case Studies • Understand the issues of professional responsibility  confidentiality  competence (not taking on jobs you aren't qualified for)  intellectual property rights  computer misuse 3) Software Processes • Know what a software process: convert sys spec into executable sys • Know the four software process activities 1) specification 2) development 3) validation: validate + test product by executing code 4) evolution: SW is flexible and can change • Understand each of the steps in the “Software Specification” overview. • Know the basic process to get from System Specification to an Executable System. • Understand the different design activities. 1)Architectural Design: id overall structure of sys 2)Interface Design: interface b/w sys components 3)Component Design: design each sys component 4)Database Design: design sys data structures and db • Know three testing stages. 1)Component Test: test indiv f(x), looking at code 2)System Test: test sys as whole (black box test) 3)Acceptance Test: test w/ customer data • Know the two software development (planning) paradigms Plan- driven Process Agile Process - aka Big Design Up Front (BDUF) - plan and document, all activities planned ahead - easier to change process to reflect changing customer req - incremental planning • Know the three software delivery (timing) options.  single delivery: delivered once and fully complete  incremental delivery: give customer incomplete ver of SW (2-4wk sprints)  continuous delivery: short cycle increments • Know the waterfall model and its phases (don’t need exact names).  single delivery  plan-driven model, w/ distinct phases, rarely any changes  must go in order can only go backwards from step 5 1. Req. definition 2. sys and SW design 3. implement and unit test 4. integration and sys test 5. operation and m