Reference no: EM133190892 , Length: 3 Pages
The first step will be to select an organization as the target for your Software Design document. This organization will be used as the basis for each of the assignments throughout the course and should conform to the following guidelines:
Nontrivial: The selected organization should be large enough to allow reasonable exercise of the software design process.
Domain knowledge: You should be familiar with the organization to allow the focus to be on the project tasks without significant time required for domain education.
Accessibility: You should have good access to the people and other information related to the organization because this will be an important part of the process.
Note: The selected organization might already have the software implemented and may still be used as the basis for the projects in this course.
Note: The selected organization must have a need for some kind of software as part of its operation. Therefore, feel free to identify a hypothetical organization that meets the requirements. Any necessary assumptions may be made to fulfill the requirements of organization selection.
Select a real or fictitious organization that fits these requirements.
Questions:
Project outline and requirements
Briefly describe the organization (can be hypothetical) where the software will be implemented.
Include the company's size, location(s), and other pertinent information.
Briefly describe the organization's software needs and an overview of the target software intended to meet the organization's needs.
The overview should identify and describe 3-4 key features of the software to become the basis for the design.
The material can be taken from the approved proposal that was submitted to instructor.
Make sure that this project is approved by the instructor.
Design methodology
Select and describe a design method to use for designing this software application project.
Explain why the design method is best for the project.
Include a description of the organization's software development environment and practices and other factors that might influence the approach that is used to design the software.
Requirements Analysis and Software Architecture
Identify and describe the organization's functional and nonfunctional requirements that are allocated to the 3-4 features you identified in the previous section.
Identify 3-4 use cases in the form of a use-case diagram.
Briefly describe each of the use cases.
Identify and describe the intended actors or users of the software.
Sequence Diagrams
Develop at least 2 data sequence diagrams for your application using the UML.
In some cases, sequence diagrams show classes that have been designed.
For this assignment, you do not need to define the classes. Instead, you only need to identify the objects that will potentially be used.
Objects are the nouns used in the program (e.g., customer, database, and invoice)
Paste the diagrams into the Software Design Document.
Describe each diagram with sufficient detail to remove any potential ambiguities and to allow a reader with minimal knowledge of the project to understand the diagram.
State Transition Diagrams
Develop at least 2 state transition diagrams for your application using the UML.
In some cases, state transition diagrams show classes that have been designed.
For this assignment, you do not need to define the classes. Instead, you only need to identify the objects that will potentially be used.
Paste the diagrams into the software design document.
Describe each diagram with sufficient detail to remove any potential ambiguities and to allow a reader with minimal knowledge of the project to understand the diagram.
Identify and describe a software architecture style to use as the basis for your software design project.
Include an explanation of why you selected the architectural style.
Describe some strengths and weaknesses of the architectural style and how those will impact your software design.
Describe the architecture of the software that you are designing in the form of a conceptual model that depicts the high-level structure of the software.