×
Log in to StudySoup
Get Full Access to WSU - CSC 4110 - Study Guide - Midterm
Join StudySoup for FREE
Get Full Access to WSU - CSC 4110 - Study Guide - Midterm

Already have an account? Login here
×
Reset your password

WSU / Computer Science and Engineering / CSC 4110 / wayne state software engineering

wayne state software engineering

wayne state software engineering

Description

School: Wayne State University
Department: Computer Science and Engineering
Course: Software Engineering
Professor: Vaclav rajlich
Term: Fall 2016
Tags: software and Engineering
Cost: 50
Name: Software Engineering - Midterm 3 Study Guide
Description: Covers chapters 11, 12, 13, 14 and 18. Material to know for the last midterm of the semester.
Uploaded: 11/16/2016
6 Pages 131 Views 0 Unlocks
Reviews


OneNote Online https://onenote.officeapps.live.com/o/onenotefram... Midterm 3 Study Guide Wednesday, November 16, 2016 4:03 PM Note: This study guide is to help you gather the materials and organize them in a way that you can study them more efficiently. Details on concepts can be found in the course content and text, as well as in uploaded notes for this course.  Chapters: 11, 12, 18, 13, 14 Ways to Study 1. Review in-class notes 2. Review PowerPoint slides 3. Read Textbook 4. Complete chapter exercises in textbook (Professor said this is the best way to prepare) 5. Create and Study Flash Cards  6. Review the quizzes 7. Copy Lecture notes or PowerPoints (writing helps commit to memory) One thing I like to do is take some sheets of paper or large index cards and write down one topic per sheet/card. As I become more familiar with certain topics, I set that aside and focus on those I need to review more. Similar to flash cards.  Topics to study based on chapter objectives These are best answered as you are reading the textbook to study • Chapter 11- Conclusion of software change ○ What is the build process and the new baseline? ○ How is software prepared for future changes? ○ What happens when a new version is released? • Chapter 12- Introduction to software processes ○ What are the granularities and forms of software processes? ○ Explain the Solo Iterative Process ○ Explain the two main work products and three main loops of SIP ○ What is the enactment and measures of SIP? ○ Explain planning in SIP • Chapter 18- Example of Solo Iterative Process ○ Know the initial development of a greatly simplified version ○ Know the two iterations of SIP given in this example • Chapter 13 – Team Iterative Processes ○ Know Agile Iterative Process ○ Know the iteration and daily loop aspects of AIP ○ Know the directed iterative process ○ Know the difference between developers and testers in DIP ○ Know the centralized iterative process ○ Know the project circumstances that require CIP and the role of architects, code owners, and quality managers in CIP • Chapter 14 – Initial Development ○ Know the software plan and its role in initial development ○ Know the elicitation and analysis of the initial product backlog ○ Know the design of the classes and their dependencies ○ What are CRC cards? ○ Know bottom-up implementation of the first version Terms to Know grouped by chapter Know these terms, their definitions, and the concepts behind them.  Note: Chapter 18 is not listed here, as it is primarily hands on and mostly requires knowledge of terms presented in chapter 12 • Build • External documentation • Annotations • Acceptance testing • Solo Iterative Process • Process • Granularity • Coarse vs fine • Agile iterative process • Programming team • Product manager • Process manager • Software change loops


○ What is the build process and the new baseline?



We also discuss several other topics like accounting 201 exam 2

1 of 3 11/16/2016 05:00 PMOneNote Online https://onenote.officeapps.live.com/o/onenotefram... • Alpha release • Beta release • General release • User manuals • Help systems granualrity • Form of a software process • Enactment • Process performance • Process plan • Iterative processes • Time management • LOC • MLOC • KLOC • Decomposition • Epics • Tasking • • Daily meeting • Iteration meeting • Iteration planning • Iteration capacity • Iteration backlog • Iteration work • Agile manifesto • Iteration review • Directed iterative process • Developers • Testers • Iteration loop • Software change loop • Build loop • Centralized iterative process • Code guardian • Architects • Quality managers • Code owners • Requirements engineers • Manual writers • Documentation writers • Network and operating system specialists • Concept locators

• Software plan • Overview • Assumptions • Constraints • Deliverables • Evolution • Range • Summaries • Reference materials • Definitions • Acronyms • Process • Organization • Technologies • Management • Cost • Initial product backlog • Requirements elicitation • Prototyping • Requirements creep • Design • Methodology • CRC card • Bottom up implementation • Dependency graph cycles • Code skeleton •


○ How is software prepared for future changes?



Don't forget about the age old question of elizabeth owens las positas

Some pointers Be able to answer questions at the end of each chapter, both those that are conceptual and those that are practical The powerpoint slides for the class serve as a good basis for general information, but questions can sometimes be specific and answers require 2 of 3 11/16/2016 05:00 PMOneNote Online https://onenote.officeapps.live.com/o/onenotefram... wording as described in the book. Make sure to read the book chapters thoroughly.  Do not make the mistake of not studying Chapter 18, the one that is a practical example. While it may not seem like there is a lot of content that you do not already know in there, there will be questions on it or relative to it.  Study with your classmates and compare your solutions to the end of chapter exercises. While there are no solutions listed in the book or recorded elsewhere, you can discuss with your classmates to determine what the correct answer is. If you are still stuck, the professor said to email him or a TA so that they can point you in the right direction.  3 of 3 11/16/2016 05:00 PMOneNote Online https://onenote.officeapps.live.com/o/onenotefram... Midterm 3 Study Guide Wednesday, November 16, 2016 4:03 PM Note: This study guide is to help you gather the materials and organize them in a way that you can study them more efficiently. Details on concepts can be found in the course content and text, as well as in uploaded notes for this course.  Chapters: 11, 12, 18, 13, 14 Ways to Study 1. Review in-class notes 2. Review PowerPoint slides 3. Read Textbook 4. Complete chapter exercises in textbook (Professor said this is the best way to prepare) 5. Create and Study Flash Cards  6. Review the quizzes 7. Copy Lecture notes or PowerPoints (writing helps commit to memory) One thing I like to do is take some sheets of paper or large index cards and write down one topic per sheet/card. As I become more familiar with certain topics, I set that aside and focus on those I need to review more. Similar to flash cards.  Topics to study based on chapter objectives These are best answered as you are reading the textbook to study • Chapter 11- Conclusion of software change ○ What is the build process and the new baseline? ○ How is software prepared for future changes? ○ What happens when a new version is released? • Chapter 12- Introduction to software processes ○ What are the granularities and forms of software processes? ○ Explain the Solo Iterative Process ○ Explain the two main work products and three main loops of SIP ○ What is the enactment and measures of SIP? ○ Explain planning in SIP • Chapter 18- Example of Solo Iterative Process ○ Know the initial development of a greatly simplified version ○ Know the two iterations of SIP given in this example • Chapter 13 – Team Iterative Processes ○ Know Agile Iterative Process ○ Know the iteration and daily loop aspects of AIP ○ Know the directed iterative process ○ Know the difference between developers and testers in DIP ○ Know the centralized iterative process ○ Know the project circumstances that require CIP and the role of architects, code owners, and quality managers in CIP • Chapter 14 – Initial Development ○ Know the software plan and its role in initial development ○ Know the elicitation and analysis of the initial product backlog ○ Know the design of the classes and their dependencies ○ What are CRC cards? ○ Know bottom-up implementation of the first version Terms to Know grouped by chapter Know these terms, their definitions, and the concepts behind them.  Note: Chapter 18 is not listed here, as it is primarily hands on and mostly requires knowledge of terms presented in chapter 12 • Build • External documentation • Annotations • Acceptance testing • Solo Iterative Process • Process • Granularity • Coarse vs fine • Agile iterative process • Programming team • Product manager • Process manager • Software change loops


○ What happens when a new version is released?



If you want to learn more check out biology 105 exam 2

1 of 3 11/16/2016 05:00 PMOneNote Online https://onenote.officeapps.live.com/o/onenotefram... • Alpha release • Beta release • General release • User manuals • Help systems granualrity • Form of a software process • Enactment • Process performance • Process plan • Iterative processes • Time management • LOC • MLOC • KLOC • Decomposition • Epics • Tasking • • Daily meeting • Iteration meeting • Iteration planning • Iteration capacity • Iteration backlog • Iteration work • Agile manifesto • Iteration review • Directed iterative process • Developers • Testers • Iteration loop • Software change loop • Build loop • Centralized iterative process • Code guardian • Architects • Quality managers • Code owners • Requirements engineers • Manual writers • Documentation writers • Network and operating system specialists • Concept locators

• Software plan • Overview • Assumptions • Constraints • Deliverables • Evolution • Range • Summaries • Reference materials • Definitions • Acronyms • Process • Organization • Technologies • Management • Cost • Initial product backlog • Requirements elicitation • Prototyping • Requirements creep • Design • Methodology • CRC card • Bottom up implementation • Dependency graph cycles • Code skeleton •

We also discuss several other topics like lgs express
Don't forget about the age old question of anatomy and physiology lecture exam 3
If you want to learn more check out organic chemistry 1 exam 3

Some pointers Be able to answer questions at the end of each chapter, both those that are conceptual and those that are practical The powerpoint slides for the class serve as a good basis for general information, but questions can sometimes be specific and answers require 2 of 3 11/16/2016 05:00 PMOneNote Online https://onenote.officeapps.live.com/o/onenotefram... wording as described in the book. Make sure to read the book chapters thoroughly.  Do not make the mistake of not studying Chapter 18, the one that is a practical example. While it may not seem like there is a lot of content that you do not already know in there, there will be questions on it or relative to it.  Study with your classmates and compare your solutions to the end of chapter exercises. While there are no solutions listed in the book or recorded elsewhere, you can discuss with your classmates to determine what the correct answer is. If you are still stuck, the professor said to email him or a TA so that they can point you in the right direction.  3 of 3 11/16/2016 05:00 PM
Page Expired
5off
It looks like your free minutes have expired! Lucky for you we have all the content you need, just sign up here