Please read the initial question on what the topic is about. Then read the other response. Finally, create a 100-150 response to the other response answer. This needs to be critical thought out reply with reference.
Part 1:
Initial Question:
Your manager recently mentioned to you that "since data flow diagrams and systems flowcharts provide redundant pictures of an information system so we don't need both. As a result, we can eliminate one of them to save time and deliver our system ahead of timer."
Do you agree with your manager? Please respond to your manager with your comment as a systems analyst.
Other response:
Flowchart and dataflow diagram describe the path of process or data step by step. Both the diagrams are made to make the process simple to understand
A flow chart provides the steps needed to reach the desired results while a data flow diagram describes the source from which data is coming, the change that occurs in the system and the source at which it ends
Flowchart
A flowchart divides down a process into simple steps by writing down the steps in boxes that are connected with arrows. A flow chart starts from the first step and ends at the last step with all the actions to be performed in middle.
Data Flow Diagram
A data flow diagram is a graphical representation of flow data through information system. It shows what kind of data will be input to the system and what data is received as the output. It also tells where the data will come from and go to and where it stored in the process.
In conclusion, both these tools provide a very easy way to understand the way a process is taking place or data is being processed from the beginning till the end. I think avoiding those tools or choosing one from the other only creates complexity and ambiguity to the life cycle of the process.
Source:
Critical Answer(Needed): 100-150 words with reference
Part 2:
Initial Question:
You are a systems analyst and you are tasked to build a new website system for a publishing company. You have a solid experience is with traditional data and process modeling techniques. Recently, you learned an object-oriented approach and you decide to try it by mixing it with the traditional structured analysis approach.
Therefore, the question is, "Can structured techniques and object-oriented techniques be mixed? How should we start? How can they be mixed? How are the tasks in this mixed approach different from traditional structured analysis?
Other response:
The traditional structured approach to process modeling begins by analyzing the interaction of an entity and data through a process. The focus is, therefore, on the processes involved in a system.
For good process analysis, there must be a full understanding of the processes that will occur, which is the product of a requirements analysis. However, the data flow diagrams produced in the traditional approach may not clearly model the processes impacting a data store or the entities acting upon them.
This is where the object-oriented approach is useful. By focusing on objects that are part of the system, such as data stores and entities, we can more effectively model what processes are needed for proper interaction between the two. To incorporate an object-oriented approach, we would first produce a use case diagram which identifies how a data store will be used and by whom. We can easily see what data stores an entity needs access to and the diverse sources acting upon a single data store.
From there, we can proceed in the traditional approach, producing processes the facilitate the interactions we have defined in the use case diagram. Furthermore, grouping processes with a data store object will assist programmers, who are likely using an object-oriented approach to coding, in identifying properties for their defined object classes.
References
Dixit, J.B. & Kumar, R. (2007). Structured system analysis and design. [Books24x7 version] Available from
Critical Answer(Needed): 100-150 words with reference
Part 3:
Initial Question:
You are a systems analyst and you are tasked to build a new website system for a publishing company. You have a solid experience is with traditional data and process modeling techniques. Recently, you learned an object-oriented approach and you decide to try it by mixing it with the traditional structured analysis approach. Therefore, the question is, "Can structured techniques and object-oriented techniques be mixed?
How should we start? How can they be mixed? How are the tasks in this mixed approach different from traditional structured analysis?
Other response:
Yes, structured techniques and object-oriented techniques can be mixed (Rickman, n.d). By combining structured techniques and object-oriented techniques we can take advantage of the strengths of both methodologies.
It means a better website system can be created by looking at the design requirements from both a structured approach and an object oriented approach. It will be easy to create a more flexible and reusable website design by tackling the system requirements from both approaches (Rickman, n.d).
We should start the mixing up of structured techniques and object-oriented techniques in the following manners (Rickman, n.d):
Build context diagram
Use functional decomposition to partition requirements
Build an OO model to understand data relationships
Build a control model to specify control
Enhance the requirements and control models to address design decisions
Group requirements and allocate all requirements, data stores and control to architecture components
Build the system flow diagram
Build the architecture interconnect diagram
Model the system performance
Iterate the above steps until a good software design has been created.
Both of these methods can be mixed in analysis phases and the design phases. The structured methods can be used for the analysis phases and the object oriented method can be implemented for the design phases (Rickman, n.d).
By using both OO techniques and structured techniques during systems analysis, a more complete understanding of the system requirements can be developed (Rickman, n.d). During the design process, the software architecture components can be designed and built either as OO modules or structured modules depending upon the requirements of the module v
The tasks in this mixed approach are different from traditional structured analysis. The tasks in a traditional structured analysis focus on the process (Rickman, n.d). On the other hand, the tasks in this mixed approach focus not only on the process but also on the data (Rickman, n.d). A lot of tasks involve understanding data, data relationships and modeling of the same in mixed approach.
Reference:
Rickman, Dale M. (n.d). A Process for Combining Object Oriented and Structured Analysis and Design. Raytheon Systems Company.
Retrieved from:
Critical Answer(Needed): 100-150 words with reference
Part 4:
Initial Question:
Discuss the relationship of the metadata model to the data in the document database.
Other response:
Before we see the relationship of metadata model and data in document database, let define the two first. According to Bachmann (2014), Metadata is data about data aim at facilitating access, management and sharing of large sets of structured and/or unstructured data. A model is a representation of a set of information.
So, metadata model is a representation of a collection of metadata information that describes a complete structure of data. A document database is a subset of a NoSQLdatabase systems designed to store semi-structured or unstructured data as documents, typically using JSON or XML format.
A document database uses documents as the structure for storage and queries.
To add additional types of data to a document database, there is no need to modify the entire database schema as there is with a relational database and data can simply be added by adding objects to the database.The flexibility of documents means that any type of data can be stored in the database and we don't need to anticipate the form of the metadata in the future.
As new metadata becomes available, it can be added to the documents with the assurance that even the most complex and deeply nested information can be represented without loss.
References:
Hess, D. (November 2014). "Managing digital asset metadata", Journal of Digital Media Management, Vol. 3, No. 2.
Bachmann,T( October 2010). Journal of Digital Asset Management Volume 6, Issue 5, pp 247-256
Critical Answer(Needed): 100-150 words with reference
Part 5:
Initial Question:
Discuss technology assisted reviews of data in a document management system
Other response:
A lot of what I found on technology assisted review (TAR) was related to e-discovery in the legal field, where it is widely used (Gricks & Ambrogi, 2015). It's a process in which large document collections are culled, coded, and characterized, and is often more reliable and cost-effective than a manual review (Gricks & Ambrogi, 2015). TAR software first is "trained" by analyzing documents coded by subject-matter experts (‘Effectiveness', n.d.).
It then applies those rules to a sample of documents, which is then assessed for quality (‘Effectiveness', n.d.). If the accuracy rate is acceptable, the remainder of the documents will be analyzed. Duke Law's EDRM has a framework for TAR (‘Technology Assisted Review', n.d.):
Setting goals
Setting protocols: These are the coding rules that will be applied
Educating the reviewers: Teaching the coding rules to the human subject experts
Coding of documents: The subject experts apply the coding rules to a sample of the documents
Predicting results: The TAR applies the coding rules to a sample of the documents
Testing results: Human reviewers validate the accuracy
Evaluating results: A review team decides if the TAR accuracy is sufficient
Achieving goals
Technology Assisted Review. (n.d.).
The Effectiveness of Technology Assisted Review. (n.d.).
Thomas C. Gricks III and Robert J. Ambrogi. (2015, November 17). A brief history of technology assisted review.
Critical Answer(Needed): 100-150 words with reference
Part 6:
Initial Question:
Discuss the relationship of the metadata model to the data in the document database.
Other response:
According to Basho, (2017,Oct 11), a document database also called a document store or document oriented database, is a subset of a type of NoSQL database. A document database is used for storing, retrieving and managing document oriented information. Unlike traditional databases, the data model in a document database is not structure in a table format of rows and columns.
A document database uses documents as the structure for storage and queries. Instead of columns with names and data type that are used in a relational database, a document contains Metadata which are description of the data type and the value for that description.
Metadata is information that describes an item of data but not its content.
Metadata is vital when it comes to the issue of unstructured data because it is through metadata that unstructured data are registered, accessed and controlled in the data warehouse environment.
The importance of metadata is best understood by noting what it typically encompasses: document ID, date of entry in the warehouse , description of the document, source of the document , index words , classification of the document , purge date , physical location reference , reference and length of the document , It is through metadata that information are determines, organizes and a manager know much about data , usually the manager look at the metadata without ever looking at the source document.
Sources:
Basho, (2017,Oct 11).document database explained.
Inmon, W.H (2005). Building the Data Warehouse , fourth edition.