40 points to answer all
lesson 4 (4.0 points)
1. what are use cases? (0.5 points)
2. list at least three topics commonly covered in software architecture documentation. (1.0 points)
3. what is a programming paradigm? (1.0 points)
4. what is object-oriented programming? (1.0 points)
5. why do software architects use flowcharts? (0.5 points)
lesson 5 (4.0 points)
1. what is code style? (1.0 points)
2. what are version control systems? (1.0 points)
3. what is a style guide? (1.0 points)
4. what is the goal of agile software development? (1.0 points)

#1 Use case diagram is one of them and its specific purpose is to gather system requirements and actors. Use case diagrams specify the events of a system and their flows.

#2 Software architecture refers to the high level structures of a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

#3 Definition. A programming paradigm is a style, or “way,” of programming. Some languages make it easy to write in some paradigms but not others. Never use the phrase “programming language paradigm.” A paradigm is a way of doing something (like programming), not a concrete thing (like a language).

#4 Object-oriented programming (OOP) refers to a type of computer programming (software design) in which programmers define not only the data type of a data structure, but also the types of operations (functions) that can be applied to the data structure.

#5 Each flow chart is concerned with one particular process or system. ... Flow charts are an important tool for the improvement of processes. By providing a graphical representation, they help project teams to identify the different elements of a process and understand the interrelationships among the various steps.

#1 Programming style, also known as code style, is a set of rules or guidelines used when writing the source code for a computer program. It is often claimed that following a particular programming style will help programmers read and understand source code conforming to the style, and help to avoid introducing errors.

#2 Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.

#3 a manual detailing the house style of a particular publisher, publication, etc.

#4 Agile software development is a process that turns a vision for a business need into solutions. We use agile because it results in software that better supports our customer needs on a faster timeline.” The Agile movement is based on the overarching goal of building software more simply.

Explanation:

20 points not 40 i need the rest

#1 Use case diagram is one of them and its specific purpose is to gather system requirements and actors. Use case diagrams specify the events of a system and their flows.

#2 Software architecture refers to the high level structures of a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

#3 Definition. A programming paradigm is a style, or “way,” of programming. Some languages make it easy to write in some paradigms but not others. Never use the phrase “programming language paradigm.” A paradigm is a way of doing something (like programming), not a concrete thing (like a language).

#4 Object-oriented programming (OOP) refers to a type of computer programming (software design) in which programmers define not only the data type of a data structure, but also the types of operations (functions) that can be applied to the data structure.

#5 Each flow chart is concerned with one particular process or system. ... Flow charts are an important tool for the improvement of processes. By providing a graphical representation, they help project teams to identify the different elements of a process and understand the interrelationships among the various steps.

#1 Programming style, also known as code style, is a set of rules or guidelines used when writing the source code for a computer program. It is often claimed that following a particular programming style will help programmers read and understand source code conforming to the style, and help to avoid introducing errors.

#2 Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.

#3 a manual detailing the house style of a particular publisher, publication, etc.

#4 Agile software development is a process that turns a vision for a business need into solutions. We use agile because it results in software that better supports our customer needs on a faster timeline.” The Agile movement is based on the overarching goal of building software more simply.

Explanation:

no backup memory