CCT202 Software Engineering

Chapter 1: Fundamentals of Software Engineering

System development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.

Agile method is a series of cycle of Requirement Engineering and Design & Implementation.

Chapter 2: Requirements Analysis Fundamentals

Q: List the guiding principles for "requirement engineering" as suggested by Davis.

Answer:

- Understand the problem before you begin to create the analysis model.

- Develop prototypes that enable a user to understand how human-machine interaction will occur.

- Record the origin of and the reason for every requirement.

- Use multiple views of requirements.

- Prioritize requirements.

- Work to eliminate ambiguity.

Chapter 4 & 5: Design

The following is a Jackson's notation of a typical report structure.

HKM is Henry-Kafura- Metric, is used to defined complexity .

It is calculated as such:

HKM = length(i) * [fin(i) * fout(i)]2

length(i) = the number of programming language statements in module i

fin = fan-in for module i

fout = fan-out for module i

Chapter 7: Software Quality Assurance (SQA) & Software Reuse

Software Quality is the conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.

Q: What is meant by Software Quality Assurance (SQA)? List the major activities associated with SQA

A: Software Quality Assurance (SQA) is a “planned and systematic pattern of actions" that are required to ensure quality in software.

SQA is comprised of a variety of tasks associated with seven major activities:

• Application of Technical Methods

  • SQA begins with a set of technical methods and tools that help the analyst to achieve a high-quality specification and the designer to develop a high-quality design.

• Conduct of Formal Technical Review

  • Activity that accomplishes quality assessment for the specification and the design. The FTR is a stylized meeting conducted by technical staff with the sole purpose of uncovering quality problems.

• Testing of Software

  • Combines a multi-step strategy with a series of test case design methods that help ensure effective error detection.

• Enforcement of standards

  • Degree in which this is applied varies from company to company. In many cases, standards are dictated by customers or regulatory mandates. In other situations, standards are self-imposed.

• Control of Change

• Measurement

  • Track software quality and asses the impact of methodological and procedural changes on improved software quality.

• Record keeping and recording

Chapter 10: Advanced Topics in Software Engineering

Q: Describe Static Web Site.

A: Static Web Sites: in its most basic form, this website is little more than a collection of static documents and tied together with links.