Software Design Document Organization and Project Selection The first step will

By
Responsive Centered Red Button

Need Help with this Question or something similar to this? We got you! Just fill out the order form (follow the link below), and your paper will be assigned to an expert to help you ASAP.

Order Form

Software Design Document
Organization and Project Selection
The first step will be to select an organization as the target for your Software Design Document. This organization and project will be used as the basis for each of the projects throughout and should conform to the following guidelines:
•    Nontrivial: The organization should be large enough and sufficiently involved in software design and development to allow reasonable exercise of the software design research and documentation process. Note that the organization does not have to be in the software design or development business, but it must have reasonable levels of software design and development activity for either internal or for external clients. The organization can be hypothetical, if necessary, and appropriate assumptions may be made. The software project should also be nontrivial and must include a database component.
•    Domain knowledge: You should be familiar enough with the organization to allow focus on the project tasks without significant time required for domain education.
•    Accessibility: You should have good access to the people and other information that is related to the project, because this will be an important part of the process.
Project
For the projects, you will be developing a Software Design Document that defines the strategies for the development project in the areas of systems requirements, analysis and design architecture.
o    Section Headings (create each heading on a new page)
    Part 1Project Outline
    Part 1: Feasibility Analysis
    Part 2: Project Planning and Risk Analysis
    Part 3: Systems Analysis
    Part 4: Data Modeling and Unified Modeling Language (UML)
    Part 5: Database Design
Part 1
•    Project Outline
o    Provide a brief description of the organization and a software development project that will be used as the basis for the projects in the course.
o    Include the company’s size, location, and other pertinent information.
o    The organization should be involved in software design and development activities for either internal or external clients.
o    The software development project must be nontrivial and must require a database component.
o    Explain the impact of the problem on the organization.
o    Describe how you intend to conduct the research on the issue and its impacts.
•    Feasibility Analysis
o    Provide a feasibility analysis for the project that will include a review of the operational, technical, and economic aspects of the project.
o    Research software development life cycles (SDLC), and select an appropriate SDLC for the project.
o    Provide a description of the major phases in the selected SDLC, and then summarize the steps within each phase as they apply to the selected project.
Part 2
For this phase, you will continue your work on the Software Design Document by adding a section for Project Planning and Risk Analysis. You will be documenting the methods that will be employed for project estimations, risk identification, and risk mitigation, and ultimately prepare the actual project plan.
The project deliverables are as follows:
•    Project Plan and Risk Analysis
o    Project plan
    Discuss the methods that will be employed to conduct project estimations, including task duration and resource identification.
    Use the estimation techniques to create a project plan, including task identification and duration, resource identification, and major milestones.
    Include a graphic image, such as a Gantt chart, to represent your project plan.
o    Risk analysis
    Discuss the methods that will be employed to conduct risk identification for the project.
    Use the risk identification methods to define the major risks to your project.
    Develop a mitigation strategy for each of the major risks.
Part 3
For this phase you will continue your work on the Software Design Document with a review and evaluation of systems analysis strategies that should be used in the selection of a design for your project. You will also provide a thorough description of the techniques that will be used to elicit system requirements.
The project deliverables are as follows:
•    Systems Analysis
o    Strategies
    Provide a description of the systems analysis strategies that should be used in the selection of a design for your project.
    Your review should include at least 2 different strategies.
    Include an analysis of the pros and cons of each strategy and a selection of the best strategy for your project including justification of your selection.
o    Requirements elicitation
    Provide a thorough description of the techniques that you will use to elicit the requirements for your project.
    Discuss how the requirements will be documented.
Part 4
For this phase, you will continue work on the Software Design Document with an analysis of the processes used in the application to determine the data requirements and to establish a proper model for the data. This is not the database design, but rather, the internal data requirements and data flow for the application.
The project deliverables are as follows:
•    Data Modeling and UML
o    Process analysis
    Describe the information-gathering techniques that you will use to obtain process and system data requirements for the application.
    This is not the database, but rather, the internal processes and required data for the application.
    Provide a description of the processes that are used in the application and the data that are required to complete those processes.
    Include use cases to depict the defined processes.
o    Data model
    Based on the information that was developed in the process analysis, prepare a data model for the application.
    The data model should include definitions of the data structures required in the application as well as UML diagrams to depict the data model. Note that much of the internal data may reside in classes that should be depicted in the model.
Part 5
For this phase, you will add a section to your design document to analyze the database requirements and prepare a strategy for the design of the database to support those requirements. Finally, you will further refine the Software Design Document to produce the final draft.
The project deliverables are as follows:
•    Database Design
o    Summarize the steps that are taken to analyze the database requirements for the application.
o    Summarize the database requirements that were developed from your analysis.
o    Provide a discussion of the approach that will be used for designing the database component of the project.
o    Justify your strategy with reference to the database requirements for the application.
•    Software Design Document
o    Review the entire document for any changes and improvements that you would like to make.
o    Ensure that this final version of the plan is sufficiently detailed to allow the organization to confidently move forward with the development of the application based on your design.

How to create Testimonial Carousel using Bootstrap5

Clients' Reviews about Our Services