Assuming you were tapped by the university president to evaluate the new enrollement system implemented this semester, enumerate your observations/comments and suggest possible areas and ways where improvements can be made. Your observations/suggestions should be properly validated with facts and literatures...(you may start with the diagrams posted in the strategic locations of the university)... (1000words)
I think the new enrollment system may have numerous advantages technically but for me as a student, I think that the new system’s procedure has a very slight difference compared from the old enrollment system. In my own opinion, I believed that more than anything else, the admin should find ways to help lessen the burden of the students in this university. I suggest that it would be better if they will also find ways to simplify the procedure and not just change the software system alone. Although it is too early to judge the new system, I believed that they should consider these factors. I believed that the newly implemented system will still undergo several revisions because the developers were only given a very limited period of time to implement the said system.
Friday, October 15, 2010
Assingnment 1 (SAD2)
Posted by ApRiL KAye BiGonTe at 12:27 PM 0 comments
Wednesday, June 9, 2010
Assignment 11 (SAD 1)
You were tasked by the IC-dean to evaluate the enrollment system of the university, list and briefly describe the characteristics that an anlayst(you) examines when choosing or defining deployment environment. (at least 500 words)
You were tasked by the IC-dean to evaluate the enrollment system of the university, list and briefly describe the characteristics that an analysts (you) examines when choosing or defining deployment environment. (At least 500 words)
It is very important to consider the deployment environment in developing a system because it helps also IT people enhance their skills.
Let me define deployment environment. As I have my research, I found out that deployment environment or application deployment environment comprises the computer hardware (specifically computer platforms), operating systems, system software, and networks that will hold up the application program.
In evaluating the enrollment system of our university there are some characteristics on the analyst in choosing the deployment environment for the particular system one of this is that
The system requirements may refer to the functional and non-functional requirements of a system that will be deployed. Conducting an analysis on system requirements would be beneficial to the future system or application that will be deployed, hardware and software interfaces and also to human involvement in the system. That is because determining the compatibility with system requirements would show whether what is needed to be given and to be done in order to run the application.
Consider the topology. As a system analyst, you have to select the best networking topologies suited for the system.
The location or area to be deploy on the system. It is essential to consider the location because this place where the developers/ analyst deploying the system. It’s clear that most of the locations in deploying the system are located in the MIS offices, server rooms, network and system’s office and sometimes the control room.
Compatibility among hardware and system software. Of course, compatibility of the application, hardware and system component must be considered. This would check whether your application has reached the minimum and/or maximum requirements on the hardware interfaces.
As an analyst, I should oversee the development, deployment, and direction of complex programs and processes as part of the tactical execution. Good communication skill is also required. Analyst must communicate clearly and concisely both on verbal and written.
Reference:
http://www.google.com.ph/url?sa=t&source=web&ct=res&cd=2&ved=0CA0QFjAB&url=http%3A%2F%2Fhercules.gcsu.edu%2F~adahanay%2Fcbis3210%2FChapter%25208-reviewQ.doc&rct=j&q=characteristics+that+an+anlayst+examines+when+choosing+or+defining+deployment+environment.&ei=7FaOS7mdBorsswOTm7HbCA&usg=AFQjCNEjAujz6gbFma0-N7KpwUDhwRvsbw
Posted by ApRiL KAye BiGonTe at 4:55 AM 0 comments
Assignment 10 (SAD 1)
With reference to assignments 8 and 9, what characteristics does an analyst (you) examine when evalauating DFD quality? (1500 words)
Before going through the characteristics that an analyst must have in order to properly evaluate a DFD, let us first define what Data Flow Diagram is and how to create it. After showing the basics of a DFD, I will enumerate and briefly explain the characteristic as based on the previous assignments.
What is a DFD?
A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design). A DFD provides no information about the timing of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the flow of control through an algorithm, allowing a reader to determine what operations will be performed, in what order, and under what circumstances, but not what kinds of data will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored (all of which are shown on a DFD).
The data flow diagram has a purpose and it provide a semantic semantic bridge between users and systems developers. And it diagrams are first graphical, eliminating thousands of words; second is logical representations, modeling WHAT a system does, rather than physical models showing HOW it does it; third is hierarchical, showing systems at any level of detail; and last jargonless, allowing user understanding and reviewing
One of the characteristic for the evaluation of the DFD quality: Completeness. DFDs offer a way to check the completeness of the process model, particularly with regards to the understanding of the data that would be required by an information system (e.g., is all the data that would be needed for input actually available? Does each processing step produce data that could be used by subsequent steps? Is all data generated usable by an information system where necessary?). DFDs can provide a fast way to generate further questions that need to be asked about the process.
All diagrams must have a basic DFD symbol present for the system.
Here are examples of symbol of a DFD using Gane and Sarson notation.
*Squares representing external entities, which are sources or destinations of data.
*Rounded rectangles representing processes, which take data as input, do something to it, and output it.
*Arrows representing the data flows, which can either, be electronic data or physical items.
*Open-ended rectangles representing data stores, including electronic stores such as databases or XML files and physical stores such as or filing cabinets or stacks of paper.
Data flow Diagram symbols:
Reference:
http://www.agilemodeling.com/artifacts/dataFlowDiagram.htm
Posted by ApRiL KAye BiGonTe at 4:52 AM 0 comments
Assignment 9 (SAD 1)
Create at least 3 different types of Data flow diagram of USEP's pre-enrollment system
Posted by ApRiL KAye BiGonTe at 4:49 AM 0 comments
Assignment 8 (SAD 1)
Using the same narrative as refelcted in your assignment 4, develop an activity diagram and a fully developed description for a use case.
Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency
Posted by ApRiL KAye BiGonTe at 4:47 AM 0 comments
Assignment 7 (SAD 1)
Consider USEP's pre-enrollment system, develop a use case diagram and write a brief use case description.
Posted by ApRiL KAye BiGonTe at 4:45 AM 0 comments
Assignment 6 (SAD 1)
Consider the following dialogue between a systems professional, John Juan, and a manager of a department targeted for a new information system, Peter Pedro:
Juan: The way to go about the analysis is to first examine the old system, such as reviewing key documents and observing the workers perform their tasks. Then we can determine which aspects are working well and which should be preserved.
Pedro: We have been through these types of projects before and what always ends up happening is that we do not get the new system we are promised; we get a modified version of the old system.
Juan: Well, I can assure you that will not happen this time. We just want a thorough understanding of what is working well and what isn’t.
Pedro: I would feel much more comfortable if we first started with a list of our requirements. We should spend some time up-front determining exactly what we want the system to do for my department. Then you systems people can come in and determine what portions to salvage if you wish. Just don’t constrain us to the old system.
Required:
a.Obviously these two workers have different views on how the systems analysis phase should be conducted. Comment on whose position you sympathize with the most.
b.What method would you propose they take? Why?
On the conversation of Juan and Pedro It is very important in planning a system to listen the both sides, Juan and Pedro and then decide what is the best for the system they have been discuss. As IT professional, he must examine the old system that company wants to do. Since, the manager has planned to develop a new system which previously ended was the modified version of old system. It professionals are mostly depend on the requirements of the client. And he ask his client to identify the possible scenarios based on the old system set by the client. As a clienthe must know the whole scenario set by the old system and he must find a best strategy and adding new requirements in order to establish the new system. Also, he experienced his past scenarios and ended up a modified version of the said system. And he ended up unsatisfied.
On creating a system there are a lot of methods would be useful to the development. There are a lot of process models which can be functional, but they should choose which can be more fitted on creating their system.
I would like to propose a Software Life Cycle Model
A software life cycle model is either a descriptive or prescriptive characterization of how
software is or should be developed. A descriptive model describes the history of how a particular
software system was developed. Descriptive models may be used as the basis for understandingand improving software development processes, or for building empirically grounded prescriptive models (Curtis, Krasner, Iscoe, 1988). A prescriptive model prescribes how a new software system should be developed. Prescriptive models are used as guidelines or frameworksto organize and structure how software development activities should be performed, and in what order. Typically, it is easier and more common to articulate a prescriptive life cycle model for how software systems should be developed. This is possible since most such models are intuitive or well reasoned. This means that many idiosyncratic details that describe how a software systems is built in practice can be ignored, generalized, or deferred for later consideration. This, of course, should raise concern for the relative validity and robustness of such life cycle models when developing different kinds of application systems, in different kinds of development settings, using different programming languages, with differentially skilled staff, etc. However,prescriptive models are also used to package the development tasks and techniques for using a given set of software engineering tools or environment during a development project. On Tactical processes help in the achievement of a plan are more concerned with the tactics to be adopted for actual plan achievement than with the development of a plan of achievement. Lastly, Implementation processes are the lowest level processes are directly concerned with the details of the what an how of plan implementation.
One of the System life cycle model
Reference:
http://www.ics.uci.edu/~wscacchi/Papers/SE-Encyc/Process-Models-SE-Encyc.pdf
Posted by ApRiL KAye BiGonTe at 4:42 AM 0 comments
