Assignment 4 (SAD2)

PRE-REGISTRATION FORM (screen shot by: Joverly Gonzales)
















SRIS (screen shot by: Joan Rose P. Dandoy)



Above images are the Pre-Registration Form and SRIS. Pre-Registration Form is a piece of paper which the enrollee needs to fill-up some inputs or information for them to have records in the corresponding colleges they have enrolled. As we can see the PRF form requires name, address, ID number, and the subject codes and descriptions. Also the students need to check the box of the sex type, type of students whether if your old, transferee or new enrollees. While in the SRIS which is the automated one requires ID number, student’s name, address, class, gender, contact email address, religion, year, type of student, desired career, parents, course, major and the subject codes and description.

Comparing the two tools of the enrolment system in the university it shows some similarity and differences in the data field. But before I will discuss that issue I will first cite the advantages of having this kind of tools for enrolment system. Using or having a Pre-Registration Form (PRF) is good, even though it is manual but it serves us a help or a guide to those encoders which they make their work easier. They will easily encode the data from the PRF to the SRIS and by this it reduce the waste of time. SRIS also has a big help to the enrolment system of the school because aside from being automated it keeps records of the students and it can easily search or track the student records if it is needed. Going back to the issue of the differences between the two tools, the Pre-Registration Form (PRF) and SRIS differ on the system interface, as I observed they has some fields in the SRIS which I cannot see in the PRF. Example of this are the religion, desired career and email address, if you are a new enrollees you need to face the encoder to fill up those fields verbally. I will suggest the uniformity of the two tools must be consistent and the layout of the two tools must be users friendly as what we call in a system, so that is readable and the student can easily understand it. Generally, Pre-Registration Form (PRF) and SRIS are has the same purpose in the enrolment system of the school, although it needs some improvements this two functions well for having a good kind of system in the enrolment.

Assignment 3 (SAD2)

Interview your university network specialist. Ask how various parts of the system communicate with each other throughout the university. (Q) Given the chance to redesign the existing setup, enumerate and discuss your key points for an effective and efficient network environment ideal for the university.
(At least 3000 words)

In this assignment we are task to interview a network analysis in our university. Engr. Ariel Roy Reyes is the assigned network analysis in the university. Supposed to be last week we have an interview schedule with Sir Reyes but unfortunately he could not make it because of some important matter. He wants to have a group or class discussion in order to share his answers to everyone. Good to say that this week he allows us to pass a questionnaire for him to answer via email. Now, I will discuss the questions with the corresponding answers from Sir Reyes.
The first question was all about the components involved in the system/s in the university including the hardware, software, technology they are using, and etc. According to Sir Reyes, he is not the right position to discuss the details of the software components used as there are other assigned personnel for such job. However, talking about hardware component and technology used, basically I, assigned as the network administrator, am entrusted to maintain our different servers to run 24/7. Currently, we have our Web Server hosted here in our University in our HP ProLiant ML350 Server. It’s an old but stable server set-up here in our Networks Office and has been active since Engr. Val A. Quimno , not yet a dean, was appointed as the Network Administrator.
The said server has the following specification:
• Intel Xeon 3.0 GHz, 3.2 GHz, or 3.4 GHz processors (dual processor capability) with 1MB level 2 cache standard. Processors include support for Hyper-Threading and Extended Memory 64 Technology (EM64T)
• Intel® E7520 chipset
• 800-MHz Front Side Bus
• Integrated Dual Channel Ultra320 SCSI Adapter
• Smart Array 641 Controller (standard in Array Models only)
• NC7761 PCI Gigabit NIC (embedded)
• Up to 1 GB of PC2700 DDR SDRAM with Advanced ECC capabilities (Expandable to 8 GB)
• Six expansion slots: one 64-bit/133-MHz PCI-X, two 64-bit/100-MHz PCI-X, one 64-bit/66-MHz PCI-X, one x4 PCI-Express, and one x8 PCI-Express
• New HP Power Regulator for ProLiant delivering server level, policy based power management with industry leading energy efficiency and savings on system power and cooling costs
• Three USB ports: 1 front, 1 internal, 1 rear
• Support for Ultra320 SCSI hard drives (six hot plug or four non-hot plug drives supported standard, model dependent)
• Internalstorage capacity of up to 1.8TB; 2.4TB with optional 2-bay hot plug SCSI drive
• 725W Hot-Plug Power Supply (standard, most models); optional 725W Hot-Pluggable Redundant Power Supply (1+1) available. Non hot plug SCSI models include a 460W non-hot plug power supply.
• Tool-free chassis entry and component access
• Support for ROM based setup utility (RBSU) and redundant ROM
• Systems Insight Manager, SmartStart, and Automatic Server Recovery 2 (ASR-2) included
• Protected by HP Services and a worldwide network of resellers and service providers. Three-year Next Business Day, on-site limited global warranty. Certain restrictions and exclusions apply. Pre-Failure Notification on processors, memory, and SCSI hard drives.
Aside from it, our mail server running under Compaq Proliant ML330 Server, our oldest server, is also hosted here in our Networks Office. Together with other Servers, such as Proxy and Enrollment Servers, both proxy and our enrollment servers are running in microcomputer/personal computers but with higher specifications to act as servers.
Next question was how the system or how do these communicate with one another, (topology, network connectivity, protocols, etc.)? According to Sir Reyes, all Servers are connected in a shared medium grouped as one subnetwork. In general, our network follows the extended star topology which is connected to a DUAL WAN Router that serves as the load balance between our two Internet Service Providers. All other workstations are grouped into different subnetworks as in star topology branching out from our servers subnetwork as in extended star topology. At present, we are making use of class C IP Address for private IP address assignments. Other workstations IP assignments are configured statically (example: laboratories) while others are Dynamic (example: offices). All workstations are connected via our proxy servers that do some basic filtering/firewall to control user’s access to the internet aside from router filtering/firewall management. So, whenever any workstation has to connect to the internet, it has to pass through software and hardware based firewall.

Next question was all about the processes involved in the communication (each system to other systems). According to Sir Reyes, as mentioned above, in item 3, all workstations are connected via a proxy server. It means that whenever a workstation is turned on, it requests for an IP address from the proxy server (for dynamically configured IP address) and connect to the network after IP address is acquired. As connection is established, each system can now communicate and share resources within the same subnetwork and to server following the concepts discuss in your Computer Network Class.

Next question was how do you go along with the maintenance of the system? According to Sir Reyes, Basically, our servers are expected to be in good condition since it is required to be up 24/7. Daily, during my vacant period, monitoring on the servers are observed that includes checking logs, checking hardware performance such as CPU health, etc. If problems are observed, remedies are then and then applied. Once in a week, regular overall checkup is observed as preventive maintenance to ensure not to experience longer downtime if possible.

Next question was the system follow a specific standard? According to Sir Reyes, as I was appointed as the Network Administrator, everything was already in place except for some minor changes. Basically, different networking standards was already observed such as cabling standards, TIA/EIA 568A-B, different IEEE standards as discussed in your Computer Networks Subject, etc.

Next question was how is the security of the system? Are there any vulnerability, risks, corresponding mitigation techniques and access control? According to Sir Reyes, as I have mentioned, we have implemented both software and hardware based filtering/firewall. Basically, Risks or vulnerabilities and different mitigation techniques were considered to increase security in our network. Aside from filtering/firewall, constant monitoring on networks activity also increases the security of the system.

And the last questions are there any interference? During what (most) times do these occur? Explain their effects especially with regards to the business of the university? According to Sir Reyes, major Interferences are normally encountered as an effect of unforeseen and beyond our control events such as black outs, and the like. The said interference would of course affect University’s day-to-day businesses for obviously this will paralyze all our activities that rely on electricity and further this might cause damage on our network devices, etc. that may later be the reason for longer downtime. Problems encountered by our providers such as connection to the National/International Gateway also affect University’s business such as correlating to University’s Business Partners outside and within the country.

Given the chance to redesign the existing setup, enumerate and discuss your key points for an effective and efficient network environment ideal for the university.

For me, if I will given a chance to redesign the existing setup of the network environment in our university I would probably improved or enhance it instead of redesigning it because in redesigning a network environment it takes time, money, and other factors which are possibly cause of failures or delays. As what Sir Reyes said he rather has some improvement and maintenance instead of redesigning another one setup of network environment. And as I observed the existing setup in network environment in the university are providing the needs of the university.

Assignment 2 (SAD2)

Relative to your answer in Assignment 1 .... what's your take on the design of the enrollment system?


From my answer in assignment 1 it was written there that the new enrollment system is much better than the old enrollment system. The administration gave their full effort to have another design in enrollment system because they noticed and observed the problems in the old enrollment system. Having a new design in enrollment system will reduce all the problems in the old one.The administration or the designer of the new system design in enrollment was using a kind of diagram to illustrate the processes or procedures. By this the students can easily understand the flow during the enrollment. But as I observed the new design was not too sensitive in delivering their understanding of the flow to the students. I cannot totally expressed the word/s in describing the design of the enrollment system in the university because all of the designer or the system analyst who were responsible for this were using their full-knowledge in creating a design of a system. Although it has some disadvantages for now, I appreciate their effort which trying their best to improve the enrollment system of the university. I think by collecting and observing the feedback of the students in their enrollment system design will challenge them to create or develop a new one which address the advantages or the problems in the existing one. We all know that we cannot have a perfect system design. They need to have a better plan which is plan to succeed.

Assignment 1 (SAD2)

Above is the diagram of the enrollment system in University of Southeastern Philippines. Based on my experienced I can say that the new enrollment system in the university is much better than the old enrollment system, because the old enrollment system consumed how many days for you to be officially enrolled in your department. I observed that this kind of delays happened because of the process and system used in the enrollment are not enough to enroll a student in the university. This must have some improvements to do in order to address the said delays. That’s why the university has a new enrollment system which they think it will address the problem in the old enrollment system. Based on my experienced again, the new enrollment system in the university takes a few days in order for the student to be officially enrolled. The process of this new enrollment system lessens the delays in the past old system in enrollment. Let’s discuss the process of this new enrollment system and provide suggestions for some improvements so that the few days of enrolling in a university will make an hour for you to be officially enrolled.


Below are the enrollment processes for the old and new students in the university:


1. (FOR NEW STUDENTS) Go to UGTO and fill up student records
2. Payment of fees (Local Council fee, OCSC fee, Headlight fee).
3. (FOR SCHOLARS) Apply/Validate scholarship at the Office of Student Services.
4. (FOR NEW STUDENTS) Enroll in ROTC or CWTS.
5. Submit or present all required documents to the adviser, and get a Pre-Registration Form.
6. Fill up the Pre-Registration form and go back to the adviser to sign it.
7. Submit the Pre-Registration form to the encoder and get the Certificate of Registration.
8. (FOR SCHOLARS) Verify student accounts at the bookkeeper. (For non-scholars) Pay tuition fee at the cashier.
9. Complete enrollment by getting stamped “Officially Enrolled” at the Registrar.
10. Apply/Validate library card.


I will discuss each of the process in enrollment and possibly put some suggestions or remedy for some improvements in the enrollment process.


1. (FOR NEW STUDENTS) Go to UGTO and fill up student records

This is the first process or first step for the new students in enrolling in the university. I think it is good and I cannot provide suggestion to it because this process is not too hassling for the new students, they must fill it up correctly because the information they input is important for the records in the UGTO.

2. Payment of fees (Local Council fee, OCSC fee, Headlight fee).

This process is the first step for the old students and the second step for the new students and this kind of hassle for the students. Based on my experienced as an old student in the university during enrollment when I reached this step I was confused because we must pay the local council fee in the other building which is where your department located and the OCSC and Headlight fee in the other building too. This kind of hassle because like me I’m a BSIT student and our building is far from the OCSC offices. What if these 3 fees will be merged in the encoding process of enrollment and the fees will reflect in the C.O.R. Even though this step is needed first in order to pass the other steps in the adviser because in the adviser’s process they collect the receipts of all the fees for you to have a PRF. By this, it will lessen the work of the adviser and the payment of these 3 fees will be made at the cashier’s office.

3. (FOR SCHOLARS) Apply/Validate scholarship at the Office of Student Services.

This step is okay with me even though it takes time because we all know the fact that almost of the students in the university are scholars. But I have some suggestion, what if the university provides more authorized people at the OSS to validate the scholarship of the students.

4. (FOR NEW STUDENTS) Enroll in ROTC or CWTS.

5. Submit or present all required documents to the adviser, and get a Pre-Registration Form.

From my suggestions in the step number 2 this step will be easy now.

6. Fill up the Pre-Registration form and go back to the adviser to sign it.

7. Submit the Pre-Registration form to the encoder and get the Certificate of Registration.

Based on my experienced when I reached this step it takes time for you to get the C.O.R because the departments is lack of resources and people (encoder), what if the respective departments at the university add encoders, I will cite an example in our department only one encoder are working to encodes all the PRF of hundreds of students. This suggestion will help to make the flow of encoding process faster.

8. (FOR SCHOLARS) Verify student accounts at the bookkeeper’s window.
(FOR NON-SCHOLARS) Pay tuition fee at the cashier’s window.

9. Complete enrollment by getting stamped “Officially Enrolled” at the Registrar.

As I observed it is good that the university provides more registrar’s window because it will cater or entertain more students during the enrollment process.

10. Apply/Validate library card.

I hope that the university will study more the situation happening during the enrollment process in using the new enrollment system which they provide. By that they will see the differences and some problems in that precious day of the students which is the enrollment day. For me, the university will also get some ideas or suggestions from the students because the students are the one who are experiencing the situation in the enrollment.

Ass.10 (SAD1)

With reference to assignments 8 and 9, what characteristics does an analyst(you) examine when evalauating DFD quality?

In order to understand a Data FLow Diagram let's first define it:

Data Flow Diagram is a “description of data and the manual and machine processing performed on the data as it moves and changes from one stage to succeeding stages of the diagram. A typical DFD doesn’t show information on how the process will operates, the sequence of the processes.

Here are some characteristics of a Data Flow Diagram to ensure quality:

1. Design and Information Flow

• Data flow-oriented design, i.e., “structured design”, defines a number of different mappings that transform information flow into program structure.

2. Two Information Flow Types

• A transform flow is a segment of a DFD that consists of an incoming flow, a transform center, and an outgoing flow.

3. Design Process Considerations

• The transition from information flow to structure is accomplished as part of a five-step process:
(1) The type of information flow is established;
(2) flow boundaries are indicated;
(3) the DFD is mapped into program structure;
(4) the control hierarchy is defined;
(5) the resultant structure is refined using design measures and heuristics.

4. Completeness

• A quality Data Flow Diagram must check the completeness of the process model, particularly in the understanding of data which are being required by the system being modeled.
5. Simplifying Complexity

In making diagram especially if the system to be modeled is a complex one, it must be ensured that items in the diagram are being simplified. One characteristic that a quality Data Flow Diagram must have is simplifying complexity by isolating some major process.

6. Symbols

One important thing to consider in quality data flow diagram is the use of correct and understandable symbols. It should be considered that in making diagrams it must follow the correct usage of symbols in naming the flows of data whether inflows or outflows

Common symbols used in Data Flow Diagrams are the following:

1. Squares representing external entities, which are sources or destinations of data.
2. Rounded rectangles representing processes, which take data as input, do something to it, and output it.
3. Arrows representing the data flows, which can either be electronic data or physical items.
4. 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.

And most of all, an analyst must know if the developer of the process model follow the stages in making DFD’s.

The normal stages are:

1. Model the current system as it is presently implemented. It is rare that a system is designed to do something entirely new.

2. The essential activities of the system are extracted. What is now left is just the data, information stores and starts and destinations. What is removed is physical things like any IT used, the media on which the data is recorded and stored, and who does what

-The DFD remaining is called the Current Logical System.
-Make minor improvements in the logic of stored data
-Combine references to data stores using replicated data
-Remove data stores which are only used because of inefficiencies in the present system

3. Eventually the new system takes physical shape according to factors like the existing IT platform it will have to operate on, the data model adopted by the organization and organizational procedures favored within the corporate culture.




References:

http://faculty.babson.edu/dewire/Readings/dfddiag.htm
www.cems.uwe.ac.uk/~gwatkins/.../04.../lec2data_flow_diagrams.doc

Ass.11 (SAD1)

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.


One of the primary considerations in developing a new information system is the application deployment environment. The application deployment environment is the configuration of computer hardware, system software, and network in which the new application software will operate. An important part of any project is ensuring that the application deployment environment is defined and well matched to application requirements. At this life cycle stage, the analyst’s goal is to define the environment in sufficient detail to be able to choose from among the competing alternatives and to provide sufficient information for design to begin. Additional details are added as design proceeds.

When choosing or defining the deployment environment, analysts are concerned with several important characteristics including the following:

• Compatibility with System Requirements. Requirements such as user locations speed of access and update, security, and transaction volume have a significant impact on environmental requirements. For example, high-volume transaction processing systems such as powerful servers, and compatible operating systems and database management systems.

• Compatibility among Hardware and System Software. Although hardware and system software compatibility has generally improved over time, it is still a significant consideration. Ensuring compatibility among hardware and system software will lessen the work on configuring system software for the sake that these sofwares will be compatible with current hardware. Besides, will also lessen the installation, since both component (system software and hardware) are compatible so there’s no need to install several drivers for compatibility sake.

• Required Interfaces to External Systems. Modern applications often interact with external systems operated by entities such as consumers, suppliers, and the government. Implementing external interfaces may require a certain system software and, less frequently, specific hardware. Example of this characteristic is the interaction between a web-based application and a typical cellular phone. In this case, system software to be used in phones is not the only concern in interacting with a web-based application; you also need to do some on the networking side.

• Conformity with the Strategic Plan and Architecture Plans. Because there are so many choices in hardware and system software organizations find it difficult and expensive to support many different types. Most medium and large-scale organizations have strategic application and technology architecture plans that focus their efforts on a limited set of hardware and software alternatives. Although that environment might not be the best for every application type, sticking to whenever possible will minimize the total cost of infrastructure maintenance and maximize the long-term compatibility among systems for that particular organization.

• Cost and Schedule. Deployment environment alternatives may vary in their impact on the project cost and schedule. Typically, environment choices that match the IT strategic plan and existing systems are the least expensive to acquire, configure and support. In deployment you need to go over with the cost, you need to be assured that upon deployment the system to be deployed will run as expected; otherwise cost problems will arise and may result to deployment failure for the system.

Reference:

http://books.google.com.ph/books?id=-ot62DeCKO4C&pg=PA292&lpg=PA292&dq=choosing%20or%20defining%20deployment%20environment.&source=bl&ots=V0x_SqKERs&sig=Td2mLV-mt4TRrO0v-1EVUKhbS64&hl=tl&ei=ppePS52NNIyqtgOWo53LCA&sa=X&oi=book_result&ct=result&resnum=10&ved=0CC4Q6AEwCQ#v=onepage&q=choosing%20or%20defining%20deployment%20environment.&f=false


My Blog: www.minenor.blogspot.com

Ass.4 (SAD1)

Identify and discuss at least 3 systems development models .. discuss each phases ... (at least 500 words/model)

Systems Development Models

A system development models help the system analyst to create algorithms of a program for the systems to be done. All the types of models has different steps to organize the building of a system. It has many types of Systems Development Models and the following are the three familiar models that we use.

1.) The Waterfall Model

For me, when I heard waterfall model it is some kind of process which is sequentially or it is be done by process. You cannot go to another phase if you cannot finish the first phase. The Waterfall Model is the earliest method of structured system development and it is still widely used.

Advantages:

The most important aspect of the waterfall model is that none of the stages can be started off with before the preceding stage is complete. The software life cycle has to follow the sequence. This type of model is easy to use and understand. Needless to mention, it is a linear model and of course, linear models are the most simple to be implemented. The amount of resources required to implement this model is very minimal. One great advantage of the waterfall model is that documentation is produced at every stage of the waterfall model development. This makes the understanding of the product designing procedure simpler. After every major stage of software coding, testing is done to check the correct running of the code.


Disadvantages:

According to a critic Schacchi this kind of model is lack of functionality. The waterfall model is said to be the easiest model to understand because it provides a sequential succession of phases to be followed but then it is not that reliable. Because of its simplicity it would only be suitable for certain classes of software development and would not work well with the other software like interactive applications. Ironically, the biggest disadvantage of the waterfall model is one of its greatest advantage. You cannot go back, if the design phase has gone wrong, things can get very complicated in the implementation phase. Many a times, it happens that the client is not very clear of what he exactly wants from the software. Any changes that he mentions in between may cause a lot of confusion. Small changes or errors that arise in the completed software may cause a lot of problem. The greatest disadvantage of the waterfall model is that until the final stage of the development cycle is complete, a working model of the software does not lie in the hands of the client. Thus, he is hardly in a position to mention if what has been designed is exactly what he had asked for

Different Phases in Waterfall Model:

Stage 1: Requirement Phase
Whether you design a small program to add two numbers or you are into developing a software system for the automation of an entire airline company, this is the first stage which can never be overridden. Unless you know what you are going to design, you cannot approach the problem. Here, the specifications of the output or the final product is studied and marked. If the software that is going to be designed should not contain certain features, for reasons like security, then it is also mentioned in this stage.

Stage 2: Specification Phase
With all the requirements and constraints in hand, a final view of how the product should exactly be, is decided. The exact way in which the software should function is mentioned in this stage.

Stage 3: Design Phase
Well, here the actual work begins. Every type of resource which will be required for the smooth designing of the software is mentioned here in this phase. What type of database will be required, what type of data should be supported, etc. are some of the important aspects that are decided in this phase. The algorithm of the process in which the software needs to be designed is made in this phase. This algorithm forms the backbone for the actual coding part in the next phase.

Stage 4: Implementation and Testing Phase
Now starts the coding part. Here, the software is designed as per the algorithm. Hence it becomes very important that the algorithm should be properly designed. The software designed as per the algorithm needs to go through constant software testing and error correction processes to find out if there are any flaw or errors. The output of this stage should be a well designed software which is at par with the algorithm designed.

Stage 5: Integration and Testing Phase
Here the various codes designed by different programmers are integrated together and is tested if the software works as per the specifications provided. The setup of the final software which needs to be installed at the clients system is also designed and tested so that the client does not face any problem during the installation of the software. The product is then handed over to the client.

Stage 6: Maintenance Phase
The work of software development does not end with the handing of the software to the client. The software designers may have to constantly provide support to the client to resolve any of the issues which may arise. There may be some flaws which get detected during the actual implementation of the project. During the maintenance phase, support and debugging is provided for all such problems.

Stage 7: New Requirements Phase
Changing times may require that the product requirements be changed. The client company may be expanding into other fields and it may want new features to be added over to the existing software. Hence, it is very important that the updated requirements be taken from the client. This requires the entire product life cycle to start all over again.

2.) The Prototyping Model

Rapid prototyping is a process wherein a working model or prototype is developed for the purpose of testing the various product features like design, ideas, features, functionality, performance and output. This process of development of working model is quite quick. The user can give an early feedback regarding the prototype. The product can be produced if the prototype meets the requirements of all designing objectives after sufficient refinement.


Advantages:

Reduction in project cost and risk.
Can be used in different industries.
Easily the errors in previous design can be detected and errors can be rectified.
Only upon the complete satisfaction the complete product is designed. Factors like manufacture ability, robustness and functionality of design are checked before sending it for production.
Greater visualization capabilities are improved right from the first stage if designing.
This helps the user in knowing how the final product will look like.
All the designing flaws can be detected easily before the manufacturing of the product starts.
Manufacturer, designer and user can discuss the product and work forward to get the best product. This helps to give the user higher output product.

Disadvantages:

Some people are of the opinion that rapid prototyping is not effective because, in actual, it fails in replication of the real product or system. It could so happen that some important developmental steps could be omitted to get a quick and cheap working model. This can be one of the greatest disadvantages of rapid prototyping. Another disadvantage of rapid prototyping is one in which many problems are overlooked resulting in endless rectifications and revisions. One more disadvantage of rapid prototyping is that it may not be suitable for large sized applications.



3.) The Spiral Model

The spiral model, also known as the spiral life cycle model, is a systems development life cycle (SDLC) model used in information technology (IT). This model development combines the features of the prototyping model and the waterfall model. The spiral model is favored for large, expensive, and complicated projects.

The steps in the spiral model can be generalized as follows:

1.The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
2.A preliminary design is created for the new system.
3.A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
4.A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second prototype; (3) planning and designing the second prototype; (4) constructing and testing the second prototype.
5.At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer's judgment, result in a less-than-satisfactory final product.
6.The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
7.The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
8.The final system is constructed, based on the refined prototype.
9.The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.

Advantages:

The spiral model is a realistic approach to the development of large-scale software products because the software evolves as the process progresses. In addition, the developer and the client better understand and react to risks at each evolutionary level.
The model uses prototyping as a risk reduction mechanism and allows for the development of prototypes at any stage of the evolutionary development.
It maintains a systematic stepwise approach, like the classic life cycle model, but incorporates it into an iterative framework that more reflect the real world.
If employed correctly, this model should reduce risks before they become problematic, as consideration of technical risks are considered at all stages.


Disadvantages:

Demands considerable risk-assessment expertise
It has not been employed as much proven models (e.g. the WF model) and hence may prove difficult to ‘sell’ to the client (esp. where a contract is involved) that this model is controllable and efficient.

Conclusion:

For me as an analyst (hehehehehe) I think I will be more detailed in using each kind of models because it depends to me and to the system if what kind of model best fit or can give a more understandable figure of a system. They has different phases to follow, advantages and disadvantages, by that I can use those factors to choose a type of model to my system. And if I choose among the 3 familiar types of model in system development I would choose WATERFALL MODEL simply because you cannot escape or jump into another phase if you are not already finish the 1st phase and lastly it is easy to use and understand.



References:

http://www.buzzle.com/articles/waterfall-model-advantages-and-disadvantages.html
http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci755347,00.html
http://scitec.uwichill.edu.bb/cmp/online/cs22l/spiralmodel.htm
http://www.rp4baghdad.com/36/prototype-disadvantages-and-rapid-prototyping-disadvantages

Ass.3 (SAD1)

Discuss the role of a systems analyst as a project manager. (at least one thousand words) .... you need to interview an analyst/project manager ..show evidences ..

April 29,2010 me and my classmates in this subject System Analyst and Design 1 was conducted an interview to the System Analyst or the Management Information System Manager in Sta. Ana Multipurpose Cooperative (SAMULCO) who is Mr. James Bautista. In my assignment 2 I explained and discuss there about the opinion and answers of Mr. James Bautista of being a System Analyst and its characteristics. We almost had a 2 hours of conversation in his office. It was a nice experienced for us because Mr. James Bautista expressed his answers very well and it brought us lessons that I can use someday.


When Mr. James Bautista started to read the set of questions he smiled to us and formally start answering it. These are the questions that we gave to him to answer:

What is your role (system analyst) as a project manager?

Mr. James Bautista explained what is the difference between a system analyst and being a project manager. He explained that most of the time a system analyst compares to a project manager. According to him a system analyst is a person who provide solutions to a problem or somewhat we call a problem-solver and also who look to the overall scope or specification of a project, overall graph a system and making design modeling like flowcharts, UML. While a project manager is a person who manages a team, manages a project, talking to the team, a client, and to interacting with the system analyst, doing the design modeling also but in his own overview, delegate or a person who speaks or acts on behalf of an organization for the team, set time-lines for the team, project and to the client and in-charge with the people, with the client and to the hardware. For him although there's a similarities of job between a system analyst and project manager but they are different. Sometimes a system analyst in a company appoint as a project manager because the company knows the capability of a system analyst of becoming a project manager. But it is not a big deal for him about the differences between the two positions.

How do you describe yourself as a project manager in your information system department or organization (in general)?

He laughed and said it was good but quiet stressful. It is good because his knowledge is very useful in this job. He can perform well with his team. Fortunately he can manage well the project and can provide a solution to it. Without the help of his team it is possible to finish and make a project because not only a system analyst and a project manager is needed in making a project. In his team there's a project manager, system analyst, programmer (developer) and a technician or familiar with the hardware. It is stressful because we all aware that the responsibility of a project manager is not easy , most of the time he use his mind thinking of some solutions and an overview of the project he was holding. He cannot stop thinking and thinking to meet the needs of a client. Overall he is happy and proud of what job he has right now.

Can you cite related experiences of being a project manager of a team in a certain project? How do you deal with it?

He cited some examples of his project he was managing in SAMULCO. In the company he is working every year there is a general assembly with the members of the cooperative. He was task to make the assembly automated or sets all the computers in the venue where the assembly was held. In his first year with the help of his team they sets and installed an estimated of 50 computers in the said venue. They brought all the computers and around 6pm before the day of the assembly they started settings and installing all the computers and finished it around 4 in the morning. It means they had less rest in that day. The following year he suggested and provided a solution that his team was not in-charge in bringing all the computers in the venue They were only in-charge in installing and settings the computer. They started at 3 in the afternoon and finished the assigned job around 12 in the midnight. It is good for them because they done it earlier than the other year. Another year in managing his team in the company's assembly. He thought that he was not fully satisfied of the result last year. He provided it another solution. He has a list of the workers in the company, he chose some of them to help his team. After choosing people to help them they provided them a training about the kind of work they will do. Fortunately, the people he chose was doing well in training and absorbed the lessons. Mr. James was happy because his team was big and around 3 in the afternoon they started settings the computers with the people he chose and finished it 7:30 in the evening. There's a big difference and good result of what Mr. James did. He also added from his experiencing he has a client who was a foreigner and didn't know how to talk English language. He can talk to his own dialect only. Sir James was worried because he cannot understand what the client wants. They only communicate in email. Sir James thought about translating the client's message in a kind of software in order to meet and understand the needs of the client. Fortunately, in 3 months of dealing with that client it has a good result. He gave us also a nice fact about the difference between a Filipino client and American client. In a project the project manager set time-lines to it, some Filipino client is not strict in the deadline or time-lines of his project but some American client is strict and wants a daily updates of his project.

What do you think are your strengths and weaknesses as a project manager?

According to Mr. James Bautista his strength is “I know what I want, I get what I want.” And his weakness is “most of the time I think like a programmer”



Overall it was a good experienced of interviewing Mr. James Bautista because if we want to become a system analyst or a project manager someday he help us by sharing his knowledge to us.

Ass.2 (SAD1)

Interview a Systems Analyst and ask what skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process [include in your answer evidences (pix, ltrs, etc)]? at least 1000 words excluding your evidences.

This assignment require us to interview a System Analyst. Before I will reveal who was the System Analyst I've interviewed and discuss his answers, I will first define a System Analyst. First thing that came out on my mind about System Analyst is a solution provider and analyzing the system well. Based on my answers in assignment 1, a System Analyst has different characteristics which is very useful. I will now reflect it to the person I've interviewed, Mr. James Bautista, a System Analyst of the Sta. Ana Multi-Cooperative (SAMULCO). Many of us came there to interview him in order for us to answer and comply the assignment 2 and assignment 3. Sir James introduced also his co-workers the programmer and the technician of the organization (SAMULCO). First, we gave him a list of questions and start the interview session.

The question was what skills and characteristics must a system analyst develop in order to be more effective in any design modeling process?

Sir James Bautista asked us what kind of design modeling process, we said that the traditional and object oriented approach modeling like UML, Data Flow Diagram. Before he answered the question, Sir James defined a System Analyst on his own. According to him a System Analyst is a person who look to the overall scope or specification of a project, overall graph a system and making design modeling like flowcharts, UML. He also mentioned that a system analyst is a solution provider or a problem solver, he told us that becoming a System Analyst must see the problem first (see the problem alone) not the solution. After seeing the problem alone that's the time you think of some possible solutions to that problem. A system analyst also must be a global thinker. He cited one example why a System Analyst must think globally and a developer (programmer) think systematically. There's a 2 men who was digging, suddenly 1 man came and ask the first man what are you doing? The first man replied “I was digging” and the man asked the second man who was digging, what are you doing? The second man replied “I will build a house.” See the difference? According to Sir James the first man is the developer (programmer) who answered he was digging and the second man is the System Analyst who answered he was building a house. Why? Because a developer (programmer) have the systematic way of thinking or he is a systematic thinker and the system analyst thinks globally or wide. A System Analyst has a wide scope of thinking how a system must be develop and what are some details he need to put into it.

After the long conversation about what is a system analyst he cited some characteristics of a system analyst must develop to be more effective in design modeling process.

Observant, system analyst must observe and think broadly to have a nice output of the system. He must consider some details on it in order to less the waste of time and resources. To meet the client's need you must be flexible of some changes and also to your environment.

Has a basic programming skills, system analyst must have this kind of skills because a good system analyst are good also in terms of programming or coding. Programming skills is important in making a project or system because how can you implement the system without this skills. A system analyst must be flexible in anything which is related to his job.

Effective Communicator, according to Sir James it is one of the important characteristic of a system analyst because you must able to communicate well to your client in order to understand what the client want. And if the system analyst communicate well to the programmer they will understand each other and has a good output to the system they are developing.

Sir James asked each one of us to add some characteristic of a system analyst. When its my turn to answer the question, I gave him a basic characteristic of a system analyst which is being patience to your work. It possibly occurs when the project he made is failed and his team member are lazy or not properly participating in the said project. System Analyst must control his temper and mood when facing or interacting people especially his client and team members. When hearing that answer Sir James laughed and say that he almost forgot some basic characteristics of a system analyst. We also asked him about the feeling of being a system analyst, he said it was a great job but quiet stressful because all the time he use his mind to think and think and think for developing a system and provide solutions to the problem. When the organization demand to him to make this kind of system he already start thinking of the possible design and solutions in order to meet the needs of the organization he is working.

This interview is one of my very great experienced as a Information Technology student because Sir James shared a lot of his experienced being a system analyst and by that I got some lessons or learning's from his experienced. It almost takes 2 hours before the interview was done. After Sir James answered all the questions , he let us speak and ask some follow up questions. But when there's no one asking him some follow up questions, he asked us if we were already experiencing a system development, we said yes, and we shared our system we'd develop in DBAD 3 the “cashiering system” he said it was a good start for us. He also gave some advise in developing a system and being a good system analyst someday.

Ass. 1 (SAD1)

Based on your learning's of chapter 1, identify and discuss some characteristics you have as a good Systems Analyst. (at least 1000 words)

As what I remember in our group reporting regarding this chapter the reporters discussed what is a System Analyst and what are the different characteristics of a good System Analyst. As what I recall, System Analyst is a person who can solve a problem using the skills and attitude they have, they can manage a project by planning and analyzing the situation of a system and the possible outcome of it. A system analyst also is researches problems, plans solutions, recommends software and systems, and coordinates development to meet business or other requirements. They will be familiar with multiple approaches to problem-solving. Analysts are often familiar with a variety of programming languages, operating systems, and computer hardware platforms. Because they often write user requests into technical specifications. Being a good System Analyst you must be a problem solver, understanding, good listener, effective communicator, knowledgeable in technology, patience sand has a management skills and technical skills. I can compare those characteristics of a good System Analyst to myself.

First, a System Analyst is a problem solver. An analyst have this kind of characteristic because it is there duty in an organization to solve a problem in a system and find best solutions to it. In my case, every time there's a problem I'm trying to solve it properly and in a good manner. Sometimes problems kills me but because of my will to solve that problem there's a way where I can find a solution to it. Problems are everywhere, so that I'm always ready to face all of them and find some solutions to it. But before solving it I will first analyze what is the cause of that problem and persons behind to it. Because if I will not considered it there's a tendency that I will fail to find solutions.

Second, a System Analyst is understanding. An analyst have this characteristic because in there profession they need it much in order to have a good result to there assignments or projects. In my case, I can say I am an understanding person because if I'm not well I have nothing. Being an understanding person is important, you need to have this characteristic in order for you to be complete. You must understand the things surrounds you. Being a student I'm not trying bu to do my best to understand every lesson I have to learn and share it. Sometimes there's a what we call misunderstanding, its cause is when a person misinterpret the act of the another person and or the situation.

Third, a System Analyst is a good listener. An analyst must have this characteristic because we know they face or meet some people (client), for them to have a good result to there project they must listen to there client very well. In my case, as a daughter I need to be a good listener to my parents for me to have better future and right path to go through. It is important for me to listen to those words from my parents because it will help me to become a good person. Words that came out from our parents are words of protection and lessons to us.

Fourth, a System Analyst is an effective communicator. An analyst is an effective communicator because of there ability to work with people and understand the problem that a system solution can solve. In my case, as a person I need to have this kind of characteristic because it helps me to find some solutions to my problem.

Fifth, a System Analyst is knowledgeable in technology. An analyst are using technologies for there projects and works. Today's generation there's a fast changing in technologies, new inventions were made and others are continue making useful and adoptive technology. In reality technologies are helping people to make the work easier. So that many of us are trying there best to practice and learn the existing technology. In my case, as a student in Bachelor of Science in Information Technology I need to have knowledge in technology. It is part of my course to study, understand and operates some kind technologies like computers.

Sixth, a System Analyst is patience. An analyst must be patience in terms of making projects. It possibly occurs when the project he made is failed and his team member are lazy or not properly participating in the sad project. System Analyst must control his temper and mood when facing or interacting people especially his client and team members.

Seventh, a System Analyst has management skills. An analyst must has this kind of skills because many of the System Analyst are also a project manager. They are managing people in an organization. It's not easy to do this kind of job because many instances will occur. If the system analyst don't know what he is doing the project of the team he manage will fail. In my case, as student in our other subject we have some groupings and sometimes I was appointed as a leader to a group. Being a leader is not easy, you need to know your members and manage your members.

Lastly, a System Analyst has technical skills. An analyst must have this kind of skills because a good system analyst are good also in terms of programming or coding. Programming skills is important in making a project or system because how can you implement the system without this skills. A system analyst must be flexible in anything which is related to his job.


It is not easy to become a System Analyst because you need to have a wide learning's which will help you in your profession. In order to be successful try your best, love your work, keep your feet on the ground and especially keep God always in your life and thanks Him for what you have now in your life.