The second part:
How can you ensure that personal information is accurate and complete? Should the contents be censored? If so, under what conditions? Describe the advantages and disadvantages and offer specific examples.
Your initial post should be succinct, of at least 300 words, and demonstrate clarity of thought and precision in writing.
The third part
Write a response for each of the following posts - they are expected to be a minimum of 150 words to clearly communicate your point of view. Offer details and explanation to support your observations. Cutting and pasting (without citing) is not welcomed in this discussion.
System Development Life Cycle (SDLC), is a model used in project management that involves a step-by-step process followed during system analysis and design (Williams & Sawyer, 2015). System analysis and design is a six-phase problem solving procedure for examining and improving an information system (Williams & Sawyer, 2015). The steps that are involved in a SDLC model are a preliminary investigation, system analysis, system design, system development, system implementation, and system maintenance (Williams & Sawyer, 2015). The reason why these steps are involved in the SDLC model is because information systems are usually revised and upgraded (Williams & Sawyer, 2015).
The phase that I find important for a successful implementation in the SDLC model is the system analysis phase. The reason why I say this is an important phase is because without data, we could not analyze data to create a report. According to our book, data is turned into information (Williams & Sawyer, 2015). That information can be crucial when creating a recommendation/conclusion in a report.
According to the book, ways that we can gather data is by reviewing current documents, interviewing managers/employees, or observe the workforce (Williams & Sawyer, 2015). Upon successfully gathering data we move onto analyzing it. The ways people can analyze data is by using models, data flow diagrams, histograms, or bar graphs (Williams & Sawyer, 2015). The reason why these graphs are used because it shows how data flowed through system. Upon gathering and analyzing data, a report created. This report could have certain objectives for example, it can show a current system works, problems of a current system, requirements for a system, or suggestions to improve a system (Williams & Sawyer, 2015). The are the steps involved in phase two for analyzing a system.
As stated above it is important for this phase because it provides very useful information into examining and improving an information system. Upon successfully implementation it can keep information systems updated, low risk to failing, policy assurance, SLA, etc. The risk involved in this phase is that if data is incorrectly gathered, then the analysis step will be incorrect. Which will lead to an incorrect report being written. Which can lead to bad decisions being made on an information system. Therefore, it is crucial to gather and collect the correct data when performing this phase. This concludes my discussion board. Hope you enjoy!
Williams, B. K., & Sawyer, S. C. (2014). Using information technology. New York, NY: McGraw Hill Education.
The most important SDLC phase is obviously the Planning Phase, because this dictates everything, the scope and objectives, functional and non-functional requirements as well as the technical, economic, and organizational feasibility. As we have heard in class before in project management there is often times a risk of “Scope Creep.” Here the risk would not even be Scope Creep but rather the wrong scope altogether. As mentioned in our book, the notable “FBI Flop.” This is where the FBI started coding for its Virtual Case File Program where it spent $170 Million dollars and created almost 1Million lines of code, only to scrap the project due to inadequate and proper scope and problem definition. Indeed, the planning phase is important. The Outputs of the planning phase are the system request, feasibility studies, project plan, functional and non-functional business requirements, they further outline the business goals for the new system. Of notable importance are the requirements. The functional requirements will be directly tied to Use Cases and subsequently to Data Flow Diagrams, these in turn will branch out to non-functional requirements which will become operational requirements which will go into program design and data storage design as part of the User Interface and User Experience. Thus we can see how it is of vital importance to get our objectives correct the first time. This is why theSystem Proposal is such an important deliverable at the end of this phase.This document compiles the detailed requirements definitions, use cases, process models, and data models together with a revised feasibility plans (economic, organizational, technical), and concluding with the work plan (Project Management).In summary in planning we are basically analyzing the current “as is system.”Then we identify improvements based on stakeholder feedback (users, management, executives, customers) and then ultimately define requirements for the new “to be system.”
Dennis et al. Systems Analysis And Design - 7th Edition.
Williams, Brian, Sawyer, Stacey. Using Information Technology.
Book I attached can be used as a reference