Describe the relationship between Software Engineering and Computer Science

CSIT425 – Describe the relationship between Software Engineering and Computer Science
CSIT 425 MidTerm Exam
Part 1: Short Answer (worth 8 points each for a total of 80 points) You will be answering 10 questions in this section by writing the BEST answer(s) for each. Note, some questions have multiple parts.
1. Describe the relationship between Software Engineering and Computer Science
2a. When we say that dependability and security are an attribute of good software, what do we mean by dependability?

b. What do we mean by security?
3. What does the principle of “people not process” mean in respect to agile development methodology?
4a. What type of data does an ethnography allows us to collect as a requirements discovery technique?
b. How would the data collected be different between doing open interviews and closed interviews as a requirements discovery technique? (Note, you’re not being asked to define the terms, bur rather, describe the resulting data from each)
5. What was the great software crisis of the 1960’s about, and why did it lead to the development of the Software Engineering discipline?
6a. When is it appopriate (theoretically) to use the waterfall process model of software engineering?
b. When is it appropriate (theoretically) to use the incremental process model of software engineering?
7a. When we talk about “completeness” as a check during Requirements Validation, what are we referring to?
b. When we talk about “realism” as a check during Requirements Validation, what are we referring to?
8. What is typically discussed in a Scrum?
9. Which types of software engineering projects are best suited for agile development approaches?
10. Briefly explain how and are being used in this diagram.
ming (worth 10 points each) Please write/draw legibly, otherwise points may be deducted if the instructor cannot interpret your handwriting or diagram. For this part of the exam, pretend that you are engineering a new customer management system (CMS) for a local pharmacy that will allow the business to receive e-prescriptions from most health care providers, will store customer health and payment data, and automate calls with pre-recorded reminders to customers when they haven’t come in to pick up their prescriptions for 2-3 days.

1. Think a little bit about the actors involved in this system (and to reduce complexity, let’s not worry about other software systems, just human actors), and their potential interactions. Map these out below by drawing a UML Use Case Diagram. Remember to utilize the notation for and as necessary.
2. For EACH of the three categories of non-functional requirements that we read about and discussed in class, write out one or more unique examples of how our pharmacy CMS might have a potential non-functional requirement. That is, for each category of non-functional requirements, provide a unique example (or examples) applicable to the CMS, and explain why each example represents that non-functional category.