Summary:You are to prepare reflection in action notes in which you address what you have learned each week that you will take forward as an Advance Practice Nurse. Entries are to be made weekly and su

System Development Life Cycle

BSA/385 Version 6

System Development Life Cycle Individual Assignment – Week One

Complete the following table:

SDLC Phases	Phase Description	Questions/Engineering Principles	Reference: Typical Documents or Artifacts used in this phase
Requirements/ Analysis	<Provide a brief description of what occurs in this phase.>	<Provide at least three questions you will need to ask to clarify what the requirements are for the program.>	Requirements Document Software Requirements Specifications (SRS) Use Cases
Design		< Using Davis’s Early Principles of Software Engineering as a guide, pick three of the 15 “most important principles” that apply to this stage.>	Software Development Plan (SDP) Data flow diagram (DFD) or entity-relationship diagram (ERD) Design Specification Technical Specification User Interface Prototype
Implementation		< Using Davis’s Early Principles of Software Engineering as a guide, pick three of the 15 “most important principles” that apply to this stage.>	Implementation Strategy Programming Conventions and Libraries Specification Implementation Schedule
Testing		<Using Royce’s top 10 principles for modern software management, pick three that apply to this stage.>	Testing Plan
Deploy/Maintenance		<Using Royce’s top 10 principles for modern software management, pick three that apply to this stage.>	Installation Guide Training Manuals

Note: An artifact is typically referred to as a by-product that is produced during the software development life cycle. Examples of architects are requirements, use cases, class diagrams, designs, project plans, test plans, etc.

Documentation in software development typically refers to user guide, training manuals, installation guide, online help, etc. Users need documentation to run the system successfully.

Artifacts can be considered as documentation that is an output from a phase in SDLC into another phase of the SDLC. For example, a requirements artifact is created by a Business Analysist during the requirements gathering phase and then passed to the Systems Analysts and the Architects to create the systems architecture and design. The same requirements artifact can also be passed to testers to create their test plans and test scenarios, as well as technical writers to create documentation outlines.

Documentation is always part of deliverables. However, artifacts may not be unless it is stated in the contract as part of custom solutions development.