Користувач:Luver/ППЗ

Технологія розробки програмного забезпечення

Цикл розробки програмного забезпечення
Програміст за роботою
Діяльність і кроки
Вимоги Специфікація Архітектура Дизайн Реалізація Тестування Розгортання Реліз Супровід
Методології Процес
Гнучка Чистого приміщення DSDM Ітеративна RAD RUP Спіраль Водоспад XP Scrum Lean V-Model FDD TDD BDD
Допоміжні дисципліни
Керування конфігурацією Документування Якість ПЗ Управління проєктами Досвід користування
Практики
Неперервна інтеграція Керована поведінкою розробка
Інструменти
Компілятор Зневаджувач Профілювальник GUI designer IDE Автоматизація складання Інфраструктура як код Тестування
Стандарти та галузі знань
CMMI ISO 9001 ITIL PMBOK SWEBOK

Проектування програмного забезпечення - це процес створення проекту та проектної документації до програмного забезпечення, що розроблюється. Також, це наука, що вивчає методології та процеси проектування.

Під проектуванням мають на увазі вироблення властивостей на основні аналізу задачі, а саме: предметної області, вимог до ПЗ. Проектувальники проводять моделювання предметної області, щоб виробити обмеження на бізнес-логіку програми та модель даних в програмі. Вимоги до ПЗ визначають зовнішні властивості програми, яка розглядається як чорна скринька.

Мета проектування - визначити внутрішні властивості системи та деталізувати зовнішні. В залежності від класу ПЗ, що створюється, процес проектування може бути як "ручним", так і декілька автоматизованим. Для проектування використовують різні графічні нотації для відображення різних аспектів системи: ER-діаграми, UML-діаграми, DFD-діаграми, та інші.

Концепції проектування

За десятки років розвитку теорії проектування програмного забезпечення, науковці на спеціалісти виробили фундаментальні концпепції проектування.

1. Абстрагування - це процес узагальнення понять за рахунок зменшення їх інформаційного змісту.

1. Refinement - It is the process of elaboration. A hierarchy is developed by decomposing a macroscopic statement of function in a stepwise fashion until programming language statements are reached. In each step, one or several instructions of a given program are decomposed into more detailed instructions. Abstraction and Refinement are complementary concepts.
2. Modularity - Software architecture is divided into components called modules.
3. Software Architecture - It refers to the overall structure of the software and the ways in which that structure provides conceptual integrity for a system. A good software architecture will yield a good return on investment with respect to the desired outcome of the project, e.g. in terms of performance, quality, schedule and cost.
4. Control Hierarchy - A program structure that represents the organization of a program component and implies a hierarchy of control.
5. Structural Partitioning - The program structure can be divided both horizontally and vertically. Horizontal partitions define separate branches of modular hierarchy for each major program function. Vertical partitioning suggests that control and work should be distributed top down in the program structure.
6. Data Structure - It is a representation of the logical relationship among individual elements of data.
7. Software Procedure - It focuses on the processing of each modules individually
8. Information Hiding - Modules should be specified and designed so that information contained within a module is inaccessible to other modules that have no need for such information.

Design considerations

There are many aspects to consider in the design of a piece of software. The importance of each should reflect the goals the software is trying to achieve. Some of these aspects are:

• Compatibility - The software is able to operate with other products that are designed for interoperability with another product. For example, a piece of software may be backward-compatible with an older version of itself.
• Extensibility - New capabilities can be added to the software without major changes to the underlying architecture.
• Fault-tolerance - The software is resistant to and able to recover from component failure.
• Maintainability - The software can be restored to a specified condition within a specified period of time. For example, antivirus software may include the ability to periodically receive virus definition updates in order to maintain the software's effectiveness.
• Modularity - the resulting software comprises well defined, independent components. That leads to better maintainability. The components could be then implemented and tested in isolation before being integrated to form a desired software system. This allows division of work in a software development project.
• Packaging - Printed material such as the box and manuals should match the style designated for the target market and should enhance usability. All compatibility information should be visible on the outside of the package. All components required for use should be included in the package or specified as a requirement on the outside of the package.
• Reliability - The software is able to perform a required function under stated conditions for a specified period of time.
• Reusability - the software is able to add further features and modification with slight or no modification.
• Robustness - The software is able to operate under stress or tolerate unpredictable or invalid input. For example, it can be designed with a resilience to low memory conditions.
• Security - The software is able to withstand hostile acts and influences.
• Usability - The software user interface must be usable for its target user/audience. Default values for the parameters must be chosen so that they are a good choice for the majority of the users.

Modeling language

A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure. A modeling language can be graphical or textual. Examples of graphical modeling languages for software design are:

• Business Process Modeling Notation (BPMN) is an example of a Process Modeling language.
• EXPRESS and EXPRESS-G (ISO 10303-11) is an international standard general-purpose data modeling language.
• Extended Enterprise Modeling Language (EEML) is commonly used for business process modeling across a number of layers.
• Flowchart is a schematic representation of an algorithm or a stepwise process,
• Fundamental Modeling Concepts (FMC) modeling language for software-intensive systems.
• IDEF is a family of modeling languages, the most notable of which include IDEF0 for functional modeling, IDEF1X for information modeling, and IDEF5 for modeling ontologies.
• Jackson Structured Programming (JSP) is a method for structured programming based on correspondences between data stream structure and program structure
• LePUS3 is an object-oriented visual Design Description Language and a formal specification language that is suitable primarily for modelling large object-oriented (Java, C++, C#) programs and design patterns.
• Unified Modeling Language (UML) is a general modeling language to describe software both structurally and behaviorally. It has a graphical notation and allows for extension with a Profile (UML).
• Alloy (specification language) is a general purpose specification language for expressing complex structural constraints and behavior in a software system. It provides a concise language based on first-order relational logic.
• Systems Modeling Language (SysML) is a new general-purpose modeling language for systems engineering.

Design patterns

A software designer or architect may identify a design problem which has been solved by others before. A template or pattern describing a solution to a common problem is known as a design pattern. The reuse of such patterns can speed up the software development process, having been tested and proven in the past.

Usage

Software design documentation may be reviewed or presented to allow constraints, specifications and even requirements to be adjusted prior to programming. Redesign may occur after review of a programmed simulation or prototype. It is possible to design software in the process of programming, without a plan or requirement analysis, but for more complex projects this would not be considered a professional approach. A separate design prior to programming allows for multidisciplinary designers and Subject Matter Experts (SMEs) to collaborate with highly-skilled programmers for software that is both useful and technically sound.

See also

• Aspect-oriented software development
• Bachelor of Science in Information Technology
• Common Layers in an Information System Logical Architecture
• Design rationale
• Interaction design
• Icon design
• Search-based software engineering
• Software architecture
• Software Design Description (IEEE 1016)
• Software development
• User experience
• User interface design
• Zero One Infinity