Friday, December 10, 2010

Why do we need to study technology/gies?

Basically, technology is there, it’s present and just roaming around somewhere. Like, the ancient times where they use carved stones for cutting and carving. Then after the carved stones where developed and became a cutting tool, such as today we call it knife, axe, and others. These where technologies that was basically based from the ancient times then was developed up to date. Simply, technology will always evolve; it will always find a new way to a simpler life.

The world wouldn’t be this better without the technological advances we had over the years. Most people admire technology because of the benefits it has given to them. The perfect reason for this is they are dependent on it. No doubt that the uses of technology and society interact strongly. Obviously, it made our lives easier to the extent that repetitive and monotonous tasks need not to be performed manually and giving us the idea to create shortcuts in working.

As simple as, the need to study technology, is to sustain the demands and needs of every mankind. The more advancement people get, the more they yearn for something much better. Reasons of studying technology also indicate how broad human knowledge is because the better the ideas the more curious humans are. At some point, technology helps in uniting people all over the world and made our communication process more interesting. And basically, technology will always continue until life ends.

Monday, December 6, 2010

I'm back with some action...

Hi guys, It's me again and I'm back in business. This time going to tackle more about technology. And the future technologies. I have a lot of things to tell you and i hope you will have fun reading it.. See you all soon. :)

Friday, September 3, 2010

PRF and the INTERFACE

Contrast and discuss the enrolment input form (PRF) with the enrolment university interface. (at least 1000words, not to include illustrations/figures/diagrams)

First of all ill let you try to observe the different illustration pertaining to the enrolment process of the university. The focus would be on the enrolment input form (PRF) and the university enrolment interface. To start, the first picture is the enrolment input form (PRF) of the university. Thanks to Charmaine Dayanan for the photo.



As you can see, this is the enrolment input form (PRF) of the old type. Here, on the top of the form is the school name and under it is the college/department with an underline. Then, you can see the name, id number, and address. And below as you can see, is the semester, school year, course, major, section, sex, type, and the scholarship that is sectioned in the first row. And below, the code, subject title, subject description, units, section, days, time, room that is labeled in the second row. And the following rows are for the filling of information. And at the bottom as you can see, are the date, student signature, and adviser. Now, let’s go to the new enrolment input form (PRF) of the university. Thanks to Chris Romarate for the photo.



As you can see, in the new enrolment input form (PRF) is just pretty the same with the old enrolment input form (PRF). The only difference is that the college/department is already named after the college which is the Institute of Computing. And the form is simpler. Lastly, we will try to see the university enrolment interface. Thanks to Joan Rose Dandoy for the photo.



As you can see, this is the enrolment interface of the university. Here, we can see the search, delete, print, new, and edit button at the top of the interface and same as the working semester and the exit button. Below, we can see the id number, the student name, address, class, gender, civil status, birth date, contact, email add, religion, year, type, desired career, college/unit, course, major, parents. In the side portion of the interface is view subjects button, official add/drop button, student’s grades button as well as the interface of the code, subject, description, unit, room, time, and days.

To compare, the interface should be the same with the enrolment input form (PRF). Or shall we say, the enrolment input form (PRF) should be the same with the interface. But, basically the interface should be the same with the enrolment input form (PRF). My points are just simple if the id number in the enrolment input form (PRF) is on the right side in the interface should also be in the right side. In the interface, you can see the working semester and in the enrolment input form (PRF) is the semester. Why shouldn’t it be semester also in the interface? The next point that I’m going to share is that the gender field in the interface while in the enrolment input form is sex? It should be gender to make it more conventional and conservative. In the interface you can see the birth date while in the enrolment input form (PRF) there is no birth date. So for me, birth date is basically part of basic information of a person so it should be included same as the religion and contact number. Lastly, the desired career in the interface should not be included because there are only 2 courses offered in the Institute of Computing which is the Bachelor of Science in Information Technology and the Bachelor of Science in Computer Science. So the desired career should not be included anymore. And the spelling of the desired career is wrong.

So basically, that’s all about it.

Friday, July 30, 2010

Network Environment of USEP

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)

Basically, all of our answers are all the same because we submitted a questionnaire to Sir Ariel Reyes as a class. We set a schedule for the interview with Sir Ariel Reyes last week but unfortunately there are problems occurred when the planned interview was about to take progress; the server had a problem so Sir Ariel Reyes needs to cut the planned session and move it to another time, but due to Sir Ariel’s busy schedule we didn’t had a chance to have a class discussion. So, the planned class discussion failed because due to some conflicts, later it turned out to be just leaving Sir Ariel Reyes a questionnaire so that he could answer all of the questions. Unfortunately, he didn’t answer all of the questions, so my answers are all base on Sir Ariel’s answers.

These were the questions that the class had come up with.

Questions:

1. In system development, how various parts of the system communicate with each other throughout the university? In what way?
2. What are the components involved in the system(s) in the university? (hardware, software, technology, etc.)
3. How do these communicate with one another? (topology, network connectivity, protocols, etc.) – may include data flow/ UML diagrams to better explain
4. What are the processes involved in the communication (each system to other systems)?
5. How do you go along with the maintenance of the system?
6. Does the system follow a specific standard? Explain Please.
7. How is the security of the system? Are there any vulnerabilities? Risks? Corresponding mitigation techniques? Access control?
8. Are there any interference? During what (most) times do these occur? Explain their effects especially with regards to the business of the university?
9. What are the current trends in network environment ideal for the university?
10. Based on your experience, can you enumerate and discuss your key points for an effective and efficient network environment that is ideal for the university?
11. Can those key points apply to the current trends for the university’s network environment? How it works?
12. Can you draw the general network architecture of the university?
13. On your own opinion, are the users satisfied with the current network setup?
14. What network architecture is used in the university?
15. What are the drawbacks that you found in the existing system? How would you treat these drawbacks?
16. On you own opinion; are there any changes that you want to change in the existing network architecture?
17. How would you see the university few years after implementing the newly developed system?

So basically, those where the questions that we had come up with and below are the answers that Sir Ariel Reyes had come up with.

• In system development, how various parts of the system communicate with each other throughout the university? In what way?

Answer of Sir Reyes:
Regarding System Development, the best person to ask is our University Programmers, Mr. Fortich and Dr. Mercado.

So here, Sir Ariel Reyes recommended Sir Japh Fortich and Maam Tammy Mercado to answer about the first question. I tried to communicate with Sir Japh but unfortunately I didn’t get him due to busy schedules.

• What are the components involved in the system(s) in the university? (hardware, software, technology, etc.)

Answer of Sir Reyes:
I am not in 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, is 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. Its 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)
-Internal storage 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 a microcomputer/personal computer but with higher specifications to act as servers.

• How do these communicate with one another? (topology, network connectivity, protocols, etc.) – may include data flow/ UML diagrams to better explain.

Answer of 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 balancer 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 users 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.

• What are the processes involved in the communication (each system to other systems)?

Answer of 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.

• How do you go along with the maintenance of the system?

Answer of 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.

• Does the system follow a specific standard? Explain Please.

Answer of 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.

• How is the security of the system? Are there any vulnerabilities? Risks? Corresponding mitigation techniques? Access control?

Answer of 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.

• Are there any interference? During what (most) times do these occur? Explain their effects especially with regards to the business of the university?

Answer of 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.

• What are the current trends in network environment ideal for the university?
• Based on your experience, can you enumerate and discuss your key points for an effective and efficient network environment that is ideal for the university?
• Can those key points apply to the current trends for the university’s network environment? How it works?
• Can you draw the general network architecture of the university?
• On your own opinion, are the users satisfied with the current network setup?
• What network architecture is used in the university?
• What are the drawbacks that you found in the existing system? How would you treat these drawbacks?
• On you own opinion; are there any changes that you want to change in the existing network architecture?
• How would you see the university few years after implementing the newly developed system?

As you can see, Sir Ariel Reyes hasn’t answered all of the questions because he explained that no time and he has a very tight schedule. Luckily, for us he manages to answer at least some of the questions.

In relevant to the second question about 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 it all begins with a plan. Plan what is the best way to improve the network environment of the university. Planning on the thing that needs to be improved, these are the requirements of the university. What are the important processes that the university really relies on, from the businesses to school related processes such as enrollment and other processes. As we all know the university has some business related establishment that currently servicing customers such as the university dormitory. In relation to network communication, do the university dormitory needs to have a better network environment for communication or are they satisfied with it? so by looking at that we can get the requirements that is needed for the improvement. Now, we go to the enrollment system of the university, does the processes satisfying? or not? So it is really base on the requirement. After the requirements are set, the next thing to do is to analyze if what are the best solutions for the requirements. Do we need to relocate the servers? Do we need to change the server? Or do we need to change the specs of the server? These are the thing that needs to be considered. So after analysis, the next thing to do is design. What are the things to do when designing? What topology are we going to use in order to attain the said requirements. What standard are we going to use in designing the network environment? So these are the questions that would basically pop out when you want to design a network environment. As the design goes on, the next thing to do is to get started.

Here are some factors that affect network performance. Unfortunately, not all networks are the same. As data is broken into component parts (often known frames, packets, or segments) for transmission, several factors can affect their delivery.

• Latency: It can take a long time for a packet to be delivered across intervening networks. In reliable protocols where a receiver acknowledges delivery of each chunk of data, it is possible to measure this as round-trip time.
• Packet loss: In some cases, intermediate devices in a network will lose packets. This may be due to errors, to overloading of the intermediate network, or to intentional discarding of traffic in order to enforce a particular service level.
• Retransmission: When packets are lost in a reliable network, they are retransmitted. This incurs two delays: First, the delay from re-sending the data; and second, the delay resulting from waiting until the data is received in the correct order before forwarding it up the protocol stack.
• Throughput: The amount of traffic a network can carry is measured as throughput, usually in terms such as kilobits per second. Throughput is analogous to the number of lanes on a highway, whereas latency is analogous to its speed limit.

These factors, and others (such as the performance of the network signaling on the end nodes, compression, encryption, concurrency, and so on) all affect the effective performance of a network. In some cases, the network may not work at all; in others, it may be slow or unusable. And because applications run over these networks, application performance suffers. Various intelligent solutions are available to ensure that traffic over the network is effectively managed to optimize performance for all users.

And also, network configuration management refers to setting, changing, collecting and restoring information about network devices (bridges, routers, workstations, servers, switches and others).
Networks of any size are in a constant state of flux. Any of the engineers responsible for the network can change the configuration of the switches and routers at any time. Configuration changes to live equipment can have devastating effects on the reliability of the network and the services provided by it. The aim of network configuration management is to save you time & reduce errors on your network due to misconfiguration of network devices. A network configuration management system is designed to allow you to take control of network changes, to simplify the job of managing networks and to fix configuration errors quickly.

There are direct correlations between properly configured devices and network security. Today's network configuration management solutions are specifically designed to automate the process of changing, securing and managing devices throughout the network. Whether configuration changes are introduced through malicious attacks, manual update errors, or network product defects, devices can become vulnerable and place the business at risk.

So, for me I would suggest that we would really have our own building that is properly located in a good space. Then, we will put up the server in that building. So that it would be spacious and the network administrators can easily move in the server room with good space for be able to make good use of the time specially when you have server crashes and server down. The more space you have the better your work is because you can free work on problems when occurred. Next would be good network architecture. The more the architecture is the better the service it can offer. Example, cables that are properly arranged makes a better connection. No entangling of wires and cables. And it can also be a very good atmosphere when you are inside the server room. Next, is good ventilation and good cooling system for all of the hardware that is currently running, the more it gives good performance. As it is all set, the next thing to do is have a more adequate server unit. I’m not against of the specs of our server but it’s kind of old and needs a better one. But, if it is still at good condition and meets the requirements needed for the university then I shall say go. But, as we all know all things has its limits, maybe we need to let it go. The next point I want to say is that the network topology. With good network topology I think all communications throughout the university will be with no problem. There will be some problems but it is minimal, and with a proper security features I think its all going to be ok. As it is all set, the next thing to do is the maintenance. Once it is operational the main thing that should be done is the maintenance. So, it should have a weekly maintenance.

One thing that I want to point out is that our network security. As Sir Val Quimno told us, the security level of our network is not very high. It is prone to all attacks and unwanted events. So for me, they really need to focus on the security so that attacks cannot penetrate the system. And it can lessen the problems in a network environment. So if this are all been done and meet I guess it’s a good network environment.

References:
http://en.wikipedia.org/wiki/Network_performance_management
http://www.networkdictionary.com/networking/ncm.php

Sunday, July 18, 2010

Relative to Assignment 1

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


As we all know that the issue of our enrollment system is the talk of the town or rather the main example of our discussions in SAD. The main thing is that all my experiences since the day I came in this University pertaining to the enrollment system of the university was satisfactory to the length that the enrollment system did change and did improve. As we all know that the University's enrollment system was one of the problems that the university is facing. The administration tried to improve the enrollment system of the University. As I stayed in this University I still have some hard time in enrolling myself in the school. Even if I am already a senior in this University still I really haven’t mastered the system yet. Although I already know the things or shall we say the processes in the enrollment system, there are still cases that confuses me. And also the time for the whole enrollment process would take me so much of the time.

So my suggestion for the design of the enrollment system?

Basically, my suggestion is simple. First is to make a formal planning among the developers of the new enrollment system. Planning is the key to all success. Planning to fail is not an option rather to plan not to fail. So planning starts with what will be the requirement, and what will be the wanted output. So if it is all set, then proceed to further study and analysis on the requirements. What are the things that are needed to be done. What are the steps in acquiring the said requirement. What are the possible way to improve the system. So, further analysis is needed to be done in order to attain the said requirement. After the analysis, go to design. So for the design, make it very simple and understandable by the users. Don’t make it complicated, just simple processes and very important processes. Eliminate unnecessary processes that would not be very relevant to the enrollment system such as to many fees to pay, why make it into one payment for better and faster process. And also, there should be one booth per department so that the process of all transactions will be more efficient especially in the finance department. So to add in the design they should be more man power for more coverage of the processes. So basically, the main thing is that, do the following things; plan, analyze, and design in order to attain the goal. But, support from the administration is also the key to have a better enrollment system for the university. So basically that’s it. Thanks..

Saturday, July 10, 2010

Accounting 2

MOVING TO DESIGN


Systems design is the process of describing, organizing, and structuring the components of a system at both the architectural level and a detailed level with a view toward constructing the proposed system. Systems design is like a set of blueprints used to build a house. The blueprints are organized by the different components of the house and describe the rooms, the stories, the walls, the windows, the doors, the wiring, the plumbing, and all other details. To understand the various elements of systems design, we must consider two questions: What are the components that require systems design? What are the inputs to and outputs of the design process?

A second important idea underlying systems design is that of the different levels of design. During analysis, we first identified the scope of the problem before we tired to understand all of the other details. We called this step top-down analysis. Analysis, as it was presented, included both top-down activities (for examples, scope first, then details) and bottom-up activities (for examples, DFD fragments first, then the middle-level diagram). The same ideas apply during design will use the term architectural design.

During the activities of the analysis phase, we built documents and models. For traditional analysis, models such as the event table, data flow diagrams, and entity-relationship diagrams were built. For object-oriented analysis, we also used the event table and developed other models such as class diagrams, use case diagrams, and use case descriptions. Regardless of the approach, the input to the design phase activities is the set of documents and models that were built during earlier phases. Design is also a model-building activity.

Designing the application architecture involves specifying in detail how all system activities will actually be carried out. These activities are described during systems analysis in great detail as logical models, without indicating what specific technology would be used. After a specific design alternative is chosen, the detailed computer processing – the physical models – can be designed. A key decision is to define the automation boundary, discussed in chapter eight, which separates the manual work done by people from the automated work done by computers.

No system exists in a vacuum. A new information system will affect many other information systems. Sometimes one system provides information that is later used by another system. Other times systems exchange information continuously as they run. The component that enables systems to share information is the system interface, and each system interface needs to be designed in detail. From the very beginning of systems design, analysts must ensure that all of these systems work together well. Some system interfaces link internal organizational systems, so the analyst may have information available about the other systems.

Designing the database for the system is another key design activity. The data model (a logical model) created during systems analysis is used to create the physical model of the database. Sometimes the database is a collection of traditional computer files. More often, it is a relational database consisting of dozens or even hundreds of tables. Sometimes files and might be used instead of relational databases. Analysts must consider many important technical issues when designing the database. Many of the technical (as supposed to functional) requirements defined during systems analysis concern database performance needs (such as response time).

During the design phase, it is important to continue creating and evaluating prototypes. Prototyping can also be used to confirm design choices about user interfaces, the database, networking architecture, controls, or even programming environments being used. Therefore, when analysts consider all of the design activities, they think about how prototypes might be used to help understand a variety of design decisions. It is also important to recognize that rapid application development (RAD) approaches develop prototypes during design that evolve into the finished system. In those cases, the prototype is the system.
A final design activity involves ensuring that the system has adequate safeguards to protect organizational assets. These safeguards are referred to as system controls. This activity is not listed last because controls have to be or it is less important than the others. On the contrary, it is a crucial activity. It is listed last because it is less important or the controls have to be considered for all other design activities – user interface, system interface, application architecture, database, and network design.

The initiation of design activities is a pivotal point in the development project. The focus changes from discovery to solution development and the whole tenor of the project changes. Coordinating all of the ongoing activities is challenging for even the best project managers because myriad details and tasks must be handled to keep the project on track. Even though analysis for iteration is essentially complete at this point, some analysis tasks remain. Every new system has a multitude of business rules that must be integrated into it missions are calculated, what happens to commissions on merchandise returns, when commissions are paid, how the commission schedule varies to encourage sales of high-margin items and sale items, and so forth.

The fundamental tool to coordinate the various project teams’ activities is the project schedule. As the activities of the design phase begin, the project manager must update the schedule by identifying and estimating all tasks associated with design and implementation, as well as any outstanding tasks associated with ongoing requirements definition. The project schedule usually must be reworked substantially to ensure that the project remains organized. Weekly, and sometimes daily, status meetings are held. If this group includes people at remote locations, teleconferencing support may be required.
As a customer support system project moves forward into design at RMO, the project team has been enhanced with the addition of new team members. Consistent with the earlier discussion, RMO initiated two new subprojects at this time, one for data conversion and one for the system and acceptance test plans. To integrate new people into the team, Barbara Halifax reorganized the structure of the project team. Those who had been on the team through-out the analysis phase are now key players in getting the new team members up to speed.

As design moves forward, the development teams begin to generate a tremendous amount of detailed information about the system. Modules, classes, data fields, data structures, forms, reports, methods, subroutines, and tables are all being defined in substantial detail. The most common and widespread technique to record and track project information is to use a CASE tool. Most CASE tools have a central repository to capture information. A major element in a CASE tool system is the central repository of information.

In chapter eight, you learned that defining the deployment environment is an activity that bridges analysis and design. The deployment environment consists of the hardware, system software, and networking environment in which the system will operate. In this section, we describe common deployment environments in detail, and in the next section we’ll explore related design patterns and architectures for application software. Single-computer architecture is an architecture that employs a single computer system executing all application-related software. A multitier architecture is an architecture that distributes application-related software or processing load across multiple computer systems. A clustered architecture is a group of computers of the same type that share a processing load and act as a single large computer system. A multicomputer architecture is a group of dissimilar computers that share processing load through specialization of function. The term centralized architecture describes deployment of all computer system in a single location.

Centralized architecture is generally used for large-scale processing applications, including both batch and real-time applications. Such applications are common in industries. Any application that has two or three of these characteristics is a viable candidate for implementation on a centralized mainframe. Current trends in conducting e-business have instilled new life into centralized mainframe computing because of the transaction volumes of many business-to-business (B2B) processes. Centralized computer systems are seldom used as the sole hardware platform for an information system. Most systems have some transaction inputs that must be accepted from geo-graphically dispersed locations and processed in real time – for example, a cash withdrawal from an ATM.

A computer network is a set of transmission lines, specialized hardware, and communication protocols that enable communication among different users and computer systems. Computer networks are divided into two classes depending on the distance they span. A local area network (LAN) is typically less than one kilometer long and connects computers within a single building or floor. The term wide area network (WAN) can describe any network over one kilometer, though the term typically implies much greater distances spanning cities, countries, continents, or the entire globe.

The internet is the infrastructure on which the Web is based. In other words, resources of the Web are delivered to users over the internet. An intranet is a private network that uses (usually members of the same organizations or workgroup). An extranet is an intranet that has been extended to include directly related business users outside the organization (such as suppliers, large customers, and strategic partners).

Simple deployment environments, such as a single centralized computer with video display terminals, can be matched to relatively simple application architectures. More complex distributed and multitier hardware and network architectures require more complex software architectures. This section describes common examples of application architectures for distributed and multitier deployment environments and the design issues and decisions associated with each. A server manages one or more information systems resources or provides a well-defined service. A client communicates with a server to request resources or services, and the server responds to those requests. Like earlier forms of client/server architecture, three-layer architecture is inherently flexible. Interactions among the layers are always requests or responses, which makes the layers relatively independent of one another. It doesn’t matter where other layers are implemented or on what type of computer or operating system they execute. The only interlayer dependencies are a common language for requests and responses and a reliable network with sufficient communication capacity.

Client/server and three-layer architecture relies on special programs to enable communication between the various layers. Software that implements this communication interface is usually called middleware. Middleware connects parts of an application and enables requests and data to pass between them. There are various methods to implement the middleware functions. Some common types of middleware include transaction processing monitors, object request brokers (ORBs), and Web service directories. Each type of middleware has its own set of protocols to facilitate communication between the various components of an information system.

The Web is a complex example of client/server architecture. Web sources are managed by server processes that can execute on dedicated server computers or on multipurpose computer systems. Clients are programs that send requests to servers using one or more of the standard Web resource request protocols. Web protocols define valid resource formats and a standard means of requesting resources and services. Any program (not just a Web browser) can use Web protocols. Thus, Weblike capabilities can be embedded in ordinary application programs.

Modern organizations rely on networks to support many different applications. Thus, the majority of new systems must be integrated into existing networks without disrupting existing applications. Network design and management are highly technical tasks, and most organizations have permanent in-house staff, contractors, or consultants to handle network administration. The analyst for a new project begins network design by consulting with the organization’s network administrators to determine whether the existing network can accommodate the new system. In some cases, the existing network capacity is sufficient, and only minimal changes are required such as adding connections for new servers or modifying routing and firewall configuration to enable new application layers to communicate.

Location-related information gathered during analysis may have been documented using location diagrams, activity-location diagrams, and activity-data matrices. During network design, the analyst expands the information content of these documents to include processing locations, communication protocols, middleware, and communication capacity. There are many different ways to describe the network infrastructure for a specific application. The diagram embodies specific assumptions about server locations, which would be decided in consultation with network administrators. The Web/application servers could have been distributed outside an establishment data center, which might have improved system response time and reduced data communication capacity requirements on the private WAN.

The network diagram is also a starting point for specifying protocol and middleware requirements. For example, the private WAN connections must support protocols required to process Microsoft Active Directory logins and queries. If the WAN fails, messages are routed through encrypted (VPN) connections over the Internet, so those connections must support the same protocols as the private WAN.

Data size per access type is an educated guess at this point in the system design because none of the software layers, interlayer communication dialogs, or database has yet been designed. So basically, that was the summary of the chapter moving to design. The points that where tackled where the issues related to managing and coordinating the design phase of SDLC. Explain the major components and levels of design, and describe each design phase activity, and describe common deployment environments and matching application architectures and lastly, develop a simple network diagram and estimate communication capacity requirements.

Thursday, July 8, 2010

Enrollment

Assuming you were tapped by the university president to evaluate the new enrollment 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)

Before I suggest my comments and observations first I will just explain to you the things that are going on in our current enrollment system. First is the enrollment procedure for the shiftees. First is that they go to the student accounts to do the following check the student account, check the balance, and then signing of their clearance. The next step would be going to his/her department to request that he/she will shift, and then the recommendation that he/she can shift to another department. Then he/she will go the new department that he/she will be transferring, and then evaluating the student, and then advising or pre-registration process. The step four is that they update the student profile. The next step would be the payment of other fees, encoding, assessment of fees, and then temporary COR (Certificate of Registration) printing. After that, the student will go to the student accounts if he/she is a scholar, and if not he/she can directly go to the cashier for the payment of the matriculation. After that process, he/she will go to the registrar to present clearance, present official receipts, and printing the student’s original COR. After that he/she is officially enrolled. The image below represents the enrollment system of the shiftees.




The next one is for the old students of the university. It is pretty the same with the enrollment system of the shiftees, the only difference is that if you are a scholar you go to the OSS office to renew your scholarship grant, but if your not a scholar then you can directly proceed to advising. Then, if your still taking up NSTP subjects you go to the office and enroll to the NSTP programs either ROTC or CWTS. After that, you go to your department for advising then encoding and printing of the temporary COR. Then, if you’re a scholar you go to the student account for posting of accounts, and if you’re a paying student you will go to the cashier to pay your matriculation. After that presenting of clearances, official receipts, and then printing of the original COR, and then you are officially enrolled. The image below represents the enrollment system of the old students.




The last thing would be for the new students. The processes are different here because the starting enrollment process is from the admission process. The student will evaluated and then if accepted they will issue an admission slip. After that you go and take the USEPAT exam and if you passed the exam you can proceed to the next step. The next step will be done in the University Guidance and Testing Office (UGTO). Encoding of student information and assigning the students ID number. After that, if the new student is a scholar he/she will go to the OSS office for scholarship application, but if you’re not a scholar then you can directly proceed to advising. Then, he/she will enroll to the NSTP programs either ROTC or CWTS. Then after that they go to the college/department that they will be enrolling and then present all the enrollment requirements, and then go for advising, paying the other fees such as local council fees and etc. then after that is the encoding and then printing of the temporary COR. If you’re a scholar you first go to the student account for posting of accounts. If not, you go to the cahiers for payment of matriculation and printing of official receipts. Then, go to the registrar then submit all the enrollment requirements such as form 137, photocopy of NSO birth certificate, USEPAT entrance exam result, admission slip, medical certificate, certificate of good moral, 2 pieces 2x2 picture, prospectus of the enrolled course, 1 piece long brown envelope and the official receipt. After that printing of the original COR and you are already officially enrolled. The image below represents the enrollment system of the new students.




So basically, those are the things that are happening if it is enrollment time in the university.

Now, the things that I notice in our enrollment system is that when you pay the other fees such as the headlight and the others is that you are going to go to their office in order for you to pay the fees. For me, I would suggest that every payment are all in one place, an example would that they’re would be one representative each office to handle such payments. Let’s take it for an example, if you’re in the IC department all payments should be handled in that department in order for a faster process. When the collection is already done that’s the time the representative will submit the payments to its office.

The other thing that I observed is that the diagrams of each enrollment system are adequately confusing such that the arrows and images seem didn’t fit. For me, I would suggest that make the diagrams more simple and understandable.
One thing that I also want to point out that if there is funds that are available for the improvement of our enrollment system why would they just make each department have their own finance office so that it would be faster if one cashier per department same goes to the registrar, one registrar booth per department.

Basically, the new enrollment system of the university had quite improved since the first day I got here. Basically, the processes are quite fast as to compare before that people in each steps wait in such long queues. But for me, still I’m not satisfied with the enrollment system of the university. I may also include factors that are involved in the said matter, maybe financial issues that no enough funds are available for such actions. As we all know cost is really a key factor in creating new systems.

I’m not really satisfied in the current enrollment system but at least some of the processes in the enrollment system had improved if not much at least in a little way.

Monday, March 8, 2010

ERP Companies




No two people see the world the same way. We invent accordingly.

HOYA Vision Care of the Americas makes and supplies ophthalmic lenses to Eye Care Professionals located within the United States, Canada, and South American countries. HOYA supplies a complete range of high quality lens designs, coatings and materials.

HOYA is tirelessly pushing ahead with the development of new lens technologies, always offering products with superior functionality and higher quality that further meet customer needs.

HOYA's complete offering of lens products includes the high index materials EYAS™ 1.60, EYNOA™ 1.67 or EYRY™ 1.70. HOYA's Phoenix™ lens material offers the broadest range of consumer benefits - it's safe, tough, light and clear.

HOYA offers superior AR lens performance through SUPER HiVision - the most scratch resistant anti-reflective coating on the market today. SUPER HiVision also automatically includes HOYA's ViewProtect, providing "easy to clean" lenses.

In the area of lens designs, HOYA offers unbeatable products such as HOYALUX iD - the world’s first integrated double-surface progressive lens design.

No matter what the needs of your patient are, HOYA has an unbeatable solution.

Mission Statement

Our Mission is to provide North America's highest quality eyewear and the industry's best customer service, to meet our customer's requirements and exceed their patient’s expectations.

Our Values

Team members who:
-Treat one another with fairness and respect
-Take accountability and ownership for failures as well as successes

A Company that:
-Believes and demonstrates that the customer is of the most importance
-Supports open and honest communications without fear of reprisal
-Celebrates its successes

A Workplace that:
-Provides the tools and resources to provide Great Quality
-Is safe from injuries and pleasant to work in
-Encourages and supports continuous improvement
-Provides training and opportunities for career advancement

HOYA Corporation Worldwide

Creating opportunities and exploiting them.

From our inception back in 1941, the HOYA Corporation has experienced remarkable growth. We intend to continue to expand our horizons in the future to be able to create and exploit new opportunities together with you, our customers.

A flexible global player.

The year 1974 heralded a period of globalization for the HOYA Corporation. Since then factories and distribution centres have been opened worldwide including our acquisition of the Buchmann group, which strengthened our position within Europe, and the integration of the North American market. All of our branches are founded on local and regional circumstances and cultural qualities, by spreading its production capacity in this way HOYA is able to operate flexibly.

It is not just a unique position from which we can provide you with new technologies and products; it is much more than that. It is also the far-reaching support that forms a central part of our working culture. In the meantime, with 46 branches in 24 countries HOYA has carved out a strong position for itself and in the process has become a flexible, global player.

This is the article that was release which is a sub company of HOYA Visions.

PRESS RELEASE - July 2009

Important step in the strategic plan of INDO a sub company of HOYA

Indo has reached a strategic agreement with the Japanese multinational Hoya.
Indo has signed an agreement with its bankers’ pool to refinance up to 85% of its bankers debt.
The Institut Català de Finances has granted a credit of 8 million euros.

Barcelona, 31 July- Commitments completed. This is what the strategic and financial alliances could be considered to be. One year ago, when Juan Casaponsa became the new Indo Executive President, Indo announced that the company initiated a major project of transformation. This project has been materializing in its two main areas: the refocusing on its three business units: lenses, eyewear and equipment, and consolidating and ensuring their financial soundness. Regarding financial soundness, just a year ago Indo made a successful capital increase. Now we can announce the agreement reached with the Banco Santander, BBVA, Bancaja, Banco de Sabadell and Banco Popular Español to refinance, in the long term, around 85% of its debt, which is equivalent to some 35 million euros. Besides, Indo has obtained a loan of 8 million euros from the Institut Català de Finances. These financing agreements underscore the trust placed in Indo’s financial future by financial entities and the Public Administration. The new approach in its three business units began with the Indo-Buchmann agreement of intent to merge their respective businesses of Equipment in order to create the new world leader in machinery. In the eyewear area, last Shareholders’ general Meeting we announced the agreement with McLaren for the design, production and worldwide marketing of its brand eyewear, which collections are avant-garde designed, innovative in materials and high added valued. In lens area, Indo reminded at a Shareholders’ General Meeting, that efforts were being made to strike-up a strategic alliance. The project has materialised with the signing of the agreement between the ophthalmic lenses divisions of Indo Lens Group and Hoya Vision Care. Hoya Corporation is the leading Japanese optical manufacturer and one of the worldwide ophthalmic lenses leaders regarding its business turnover. It also has other business areas such as Information Technology, Medical and Image Systems. Hoya Vision Care is one of its most important divisions, with its head office in Holland, and it is especially known for being a reference in high-index lenses, hardening and non-reflecting treatments for lenses and its products are among the most technologically advanced. This alliance will allow the interchange and supply of technology and of products, as well as collaboration in matters of research and development between the two companies. The agreement, which will be valid until the end of 2015 and which is extendable, states that Hoya will contribute 15 million euros to purchase technology and that Indo Lens Group will buy approximately 25% - 30% of its supply needs each year from Hoya Vision Care, especially in semi-finished products currently purchased from various sources of supply around the world. A key aspect of the agreement is that the two companies will continue to compete independently in all the markets, maintaining differentiated commercial strategies and complete independence in the management of each company. Juan Casaponsa, Indo's Executive President, considers that this strategic alliance will allow Indo “to substantially improve its structure of costs, making the most of synergies in R&D and offering the customer a wider and more innovative portfolio of products. Thanks to the association with Hoya, Indo will also benefit in scale, meaning that it will open the door to increasing its international presence with the entry into new markets". “The initiated transformational approach and the new new strategic business plan, will now be developed in detail once they have secured the foundations”

About Hoya Corporation

Since its creation in 1941 in Japan, Hoya Corporation has been the leading manufacturer of ophthalmic lenses. The Japanese giant company, which is listed in the first section of the Tokyo Stock Exchange, has diversified its business areas to also include information technology, medical systems and imaging. With more than 32,000 employees and 100 subsidiaries, Hoya Corporation registered total sales of 454.1 billion Japanese yen in the fiscal year 2009 (04/08 - 03/09). Hoya Vision Care Europe is responsible for the regional management of the Vision Care division, logistics centre, sales and marketing activities, dealing with European subsidiary companies and export activities in Europe, the Middle East and North and South Africa. The Spanish subsidiary company had a turnover of 26 million euros in 2008. About Indo International Indo is a Spanish multinational company dedicated to manufacturing and commercializing lenses, eyewear, sunglasses and equipment for opticians and ophthalmologists. Indo has more than 70 years' experience in the optical sector and is one of the leaders in the Spanish market. The group has subsidiary companies in the United States, France, Italy, Portugal, Morocco, India and Chile and has production centres in Spain, China and Thailand. Indo exports its products to more than 80 countries.

So to define Enterprise resource planning (ERP) is an integrated computer-based system used to manage internal and external resources including tangible assets, financial resources, materials, and human resources. It is a software architecture whose purpose is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders. Built on a centralized database and normally utilizing a common computing platform, ERP systems consolidate all business operations into a uniform and enterprise wide system environment.
An ERP system can either reside on a centralized server or be distributed across modular hardware and software units that provide "services" and communicate on a local area network. The distributed design allows a business to assemble modules from different vendors without the need for the placement of multiple copies of complex, expensive computer systems in areas which will not use their full capacity.

While SDLC Systems Development Life Cycle (SDLC) is a logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.
Computer systems are complex and often (especially with the recent rise of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, a number of systems development life cycle (SDLC) models have been created: "waterfall"; "fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and stabilize".
SDLC models can be described along a spectrum of agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid changes along the development cycle. Iterative methodologies, such as Rational Unified Process and Dynamic Systems Development Method, focus on limited project scopes and expanding or improving products by multiple iterations. Sequential or big-design-upfront (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks to successful and predictable results.
Some agile and iterative proponents confuse the term SDLC with sequential or "more traditional" processes; however, SDLC is an umbrella term for all methodologies for the design, implementation, and release of software.
In project management a project can be defined both with a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004) "the project life cycle encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements”.

References:
http://www.hoyavision.com/home.aspx
http://linux.sys-con.com/node/160739
http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle
http://en.wikipedia.org/wiki/Enterprise_Resource_Planning
http://docs.google.com/viewer?a=v&q=cache:UkGw6w1qSZAJ:www.hoya.be/dn.php%3Fid%3D97394%26m%3D0%26dm%3D1+HOYA+Vision+Project+Plans&hl=tl&gl=ph&pid=bl&srcid=ADGEEShu0URvoO1EEGlSrwvYAxIIlNYFGVd1tF5ITvyURciqhzMgHZC47WsP0NcklSVqIafVNOZAmnI5JscNw3t1FtsV1TQVweVABfcLVo-3S6qn7Amd48hP0Mw8Wl64mNgusN-hsGd-&sig=AHIEtbTQmSzG2fe01uKDyR-4o-801re00A

Deployment Environment

You were tasked by the IC-dean to evaluate the enrollment system of the university, list and briefly describe the characteristics that an analyst (you) examines when choosing or defining deployment environment.

So basically, my idea is that use open source servers because the primary benefit of open source is that it is free. Also considering the university which lacks in budget allocation should really be advisable to use open source servers. But I’m not against package servers my point only is that we consider the budget allocation of the university. But for me, as to evaluate I think I would use Microsoft package servers because it’s the most commonly used servers. So I basically choose the SharePoint 2007. For organizations preparing to deploy SharePoint™ 2007 or to move from a pilot to full deployment, creating a properly designed environment is critical to the successful deployment of an enterprise business productivity infrastructure. The purpose of the SharePoint Environment Design and Deployment is to create a design and project plan that will meet the organizations requirements and leverages Microsoft and DataLan standards and best practices around the following areas: Physical Architecture, Logical Layout, Security Configuration, Connectivity Planning, Usability Planning, Disaster Prevention and Recovery Planning.

• Physical Architecture – This includes the physical layout of the servers and network elements needed for the SharePoint environment. Physical architecture considerations will include:

o SharePoint Server Farm Topology Configuration
o Third Party and Custom Service Configuration
o Server specifications and allocations
o Network integration points with other systems
o Network entry/boundary points

• Logical Layout – This includes the logical layout of the SharePoint web application and service elements needed for the environment. The logical layout review addresses:

o Web application, site collection and site structure and configuration
o Shared Services and My Site placement and configuration

• Security Configuration – This outlines the security mechanisms that will be employed to control access to the environment and environment resources including:

o Environment access method and AD integration
o Content access, control, and governance
o Security delegation
o Auditing and Policy management requirements

• Connectivity Planning – Details the environment access points and user connectivity methodology and controls. Connectivity planning includes:

o Local connectivity approach planning
o Remote user connectivity approach planning

• Usability Planning – Details the usage for the environment and reviews application needs and plans. Usability planning includes:

o User experience and usage of the environment will be reviewed
o Application planning will be performed in order to identify those applications to be created within or migrated into the environment

• Disaster Prevention and Recovery Planning – Including the protection of the environment from potential service interruptions or loss of data in the event of a disaster. This planning includes:

o Environment disaster methodology creation based on SLA requirements
o Environment backup requirement levels
o Environment Monitoring requirements and solution architecture

The deliverables include:

• SharePoint environment architecture document detailing all aspects of the environmental architecture
• Deployment of the SharePoint environment based on the Enterprise Architecture Plan
o Installation of a SharePoint small or medium farm environment
o Documentation of the installation and configuration of the SharePoint environment

But I’m not closing my doors to any suggestions or alternatives, maybe in my own opinion this is the deployment environment that I would suggest to them to be defined and used.

References:
http://sharepoint.microsoft.com/Pages/Default.aspx
http://www.datalan.com/Solutions/Pages/Design%20and%20Deployment.aspx

Evaluating DFD Quality

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

Before going to the point I will just discuss about what Data Flow Diagram is:

As information moves through software, it is modified by a series of transformations. A data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The basic form of a data flow diagram, also known as a data flow graph or a bubble chart, is illustrated in Figure 1. The data flow diagram may be used to represent a system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as well as information flow modeling. In so doing, it satisfies the second operational analysis principle (i.e., creating a functional model). A level 0 DFD, also called a fundamental system model or a context model, represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively. Additional processes (bubbles) and information flow paths are represented as the level 0 DFD is partitioned to reveal more detail. For example, a level 1 DFD might contain five or six bubbles with interconnecting arrows. Each of the processes represented at level 1 is a sub function of the overall system depicted in the context model. As has been noted earlier, each of the bubbles may be refined or layered to depict more detail.

As information moves through software, it is modified by a series of transformations. A data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The basic form of a data flow diagram, also known as a data flow graph or a bubble chart. The data flow diagram may be used to represent a system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as well as information flow modeling. In so doing, it satisfies the second operational analysis principle (i.e., creating a functional model). A level 0 DFD, also called a fundamental system model or a context model, represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively. Additional processes (bubbles) and information flow paths are represented as the level 0 DFD is partitioned to reveal more detail. For example, a level 1 DFD might contain five or six bubbles with interconnecting arrows. Each of the processes represented at level 1 is a sub function of the overall system depicted in the context model. As has been noted earlier, each of the bubbles may be refined or layered to depict more detail.

Data flow diagrams defined

Data flow diagram is a geographical tool that shows, process, flows, stores and external entities in a system. Dataflow diagram shows the transformation of data into a system. DFD has got the following symbols

Process flow diagrams

Process symbol has got the following entities, process number (tells the number of the process), locality (where activity is happening) and a process name

Data flow datagram process symbol rules

• It symbolizes the transformation of data
• There must be data flowing into/out of the process
• Process can have several inputs to it or output to it
• Process with no out becomes a null process

Data store Symbol

Consist of the following entities, data store number and name of data store. The function of data store is to designate the storage of data in a DFD diagram

Rules of Data store

• DFD data store do not by level but they may reappear incase needed
• The symbol and the numbering remain the same

Data flow symbol

Data flow symbol may appear in different shape and they signify the movement of data. They do not signify the movement of people, goods etc

• Doubles arrows signifies that activities occur at the same time which is wrong
• Data flow in is never equal to data flow out

Extended entity symbol

Extended entity is sources and destination of data. This means that source is the origin and destination is the sink of data

Dos and Don’ts of external entity
• External entity never communicate with each other, this signify that there is no need for the process
• External entity should not communicate directly with data store because external entities can be identifier with the record of files and databases

How to develop Logical data flow diagram

Below are the guidelines in developing data flow diagrams
1. Develop a physical DFD
2. Explore the process for more details
3. Maintain consistency between the process
4. Following meaningful leveling convention
5. Ensure that DFD diagrams clarifies what is happening in the system
6. Remember DFD audience
7. Add control on the lower level DFD only
8. Assign meaningful level
9. Evaluate DFD for correctness

Step in drawing DFD diagrams
1. Make a list of all business activities and use it to determine the various external entities, data flows, process and data store
2. Create a context diagram which shows external entity and data flows to and from the system
3. Do not show any detailed process or data store
4. Draw diagram zero or the next level to show process but keep them general. Show data stores and the level
5. Create a child diagram for each of the process in diagram zero
6. Check for errors and make sure the levels you assign to each process and data flow are meaningful
7. Develop a physical DFD diagram from the logical DFD and distinguish between the manual and automated protocol, describe actual files and report by name and controls to indicate when the process are complete or errors occurs
8. Portion the physical DFD by separating or grouping parts of the diagram in order to facilitate programming and implementation

Advantages of data flow diagrams
• It gives further understanding of the interestedness of the system and sub-systems
• It is useful from communicating current system knowledge to the user
• Used as part of the system documentation files
• Dataflow diagram helps to substantiate the logic underlining the dataflow of the organization
• It gives the summary of the system
• DFD is very easy to follow errors and it is also useful for quick reference to the development team for locating and controlling errors

Disadvantages of data flow diagram
• DFD is likely to take many alteration before agreement with the user
• Physical consideration are usually left out
• It is difficult to understand because it ambiguous to the user who have little or no knowledge

So basically, these are the characteristics that a system analyst must have in order to evaluate the Data Flow Diagram with quality. The system analyst must have a good background of what are the systems that existed and he should also be able to identify what are those processes that a system must have with regarding to the goals of the organization. And also, an analyst must gather important information in order to have sufficient information in making the DFD. And he also must have enough background on what is their business processes. Good communication skills as well as good critical thinking. And lastly, being able to adapt to change, as we all know we are in the fast changing world or era. Well, that’s it. These are the characteristics that a good system analyst must have in order to evaluate the DFD with quality.


References:
http://hubpages.com/hub/What-is-a-data-flow-diagram

Sunday, March 7, 2010

Common Frustrations

What are the two most frequently experienced causes of frustration of IS professionals and users while working on an IS plan?

So before I answer the question I will just share some ideas about what are those common frustrations of IS professionals and users while working on an IS plan.

Use of technology often has unpleasant side effects, which may include strong, negative emotional states that arise during interaction with computers. Frustration, confusion, anger, anxiety and similar emotional states can affect not only the interaction itself, but also productivity, learning, social relationships, and overall well-being. This paper suggests a new solution to this problem: designing human–computer interaction systems to actively support users in their ability to manage and recover from negative emotional states. An interactive affect–support agent was designed and built to test the proposed solution in a situation where users were feeling frustration.

The agent, which used only text and buttons in a graphical user interface for its interaction, demonstrated components of active listening, empathy, and sympathy in an effort to support users in their ability to recover from frustration. The agent's effectiveness was evaluated against two control conditions, which were also text-based interactions:

1. Users’ emotions were ignored,
2. Users were able to report problems and ‘vent’ their feelings and concerns to the computer

Behavioral results showed that users chose to continue to interact with the system that had caused their frustration significantly longer after interacting with the affect–support agent, in comparison with the two controls.

These results support the prediction that the computer can undo some of the negative feelings it causes by helping a user manage his or her emotional state. Some problems stem from the users’ lack of knowledge, poor training, or unwillingness to read instructions or take tutorials. Often frustration results that from flaws in the computer hardware, software, networking, troubling interactions among components supplied by diverse manufacturers, or the result of malicious actions by other users.

A number of preliminary research steps are necessary to guide developers who are working on the goal of making computer usage less frustrating for users. A first step is to gain a better understanding of what frustrates users of computers. Then taxonomies of frustrating experiences can be developed and means to measure their severity and frequency can be identified. These three steps should lead to solutions with enough supporting evidence so that requests for improvements will be well received by all parties involved. Computers can be valuable tools, and networked resources via the Internet can be beneficial to many different populations and communities.

Many e-commerce and e-business firms today are turning to systems planning and systems analysis. Such analysis provides a broader view of organization catering to system development. System development activity aids in producing information systems solutions and provides a platform for resolving organizational problems using information systems. The paper puts light on objectives, management challenges faced by an organization, and road map indicating direction of systems development.

Another thing working on information systems plan takes patience and perseverance. In order to have a good outcome, IS professionals should do profound analysis and must consider a variety of factors. Without a thorough understanding of the problem and organization’s need the IS plan is intended to solve, and without knowledge of the best practices for organizing the required data, the implemented IS plan becomes an unwieldy beast that requires constant attention. Developing an IS plan is never an easy task. That is why there are methods that IS professionals try to follow and standards they try to thrash out. IS plan should serve the company and the users the way it is expected. Learning from my experience from the previous semester, IS professionals’ task does not end with a scrutiny of the information systems. Indeed, they must evaluate the entire message in terms of coherence, the quality of hanging together in the IS plan. To achieve its purpose, statements must be organized appropriately. They must be ordered in a logical manner and should support the business plan of the organization so that the transition between each one contributes to the overall objective of the plan. After answering the first question, my next purpose is to respond to the next question, “What are the two most frequently experienced causes of frustration in IS professionals and users while working on an IS plan?”

According to Freud, it is not simply the nature of the frustrating incident that determines how people will react to it. Rather, there is interplay between the situation and the psychological characteristics of individuals. The level of maturity of the individual also plays a part in the reactions to frustration (Barker, Dembo, & Lewin, 1965). With maturity, there is an increase in the variety of responses to a situation employed by individuals, in the control of the environment, and in their ability to employ problem-solving behavior and plan steps to obtain the goal. It would appear that learning, which is culturally determined, is a major factor in developing socially acceptable responses to frustration.

Frustration occurs when there is a condition, which interferes with or stops the realization of a goal. It makes us feel useless or worthless. Any interruption to our action or task can be very frustrating. Level of frustration experienced by an individual clearly can differ depending on the circumstances surrounding the frustrating experience and on the individuals themselves. There could be so many causes that lead an IS professional to frustration. Same thing happened to me. I made a list of my goals, when and how to attain those goals. I made my own schedule to help me budget my time and succeed in attaining the goals. But then the outcome was in contrast to what I had expected. I thought if I took those actions then all things would go right. This time, I should say that I am not a good planner but I will still keep on trying. I made a realization that the failure was not because I failed to plan and not because I planned to fail but there was something missing and I have to find out what it was. I learned from that experience and I should do the right thing next time.

Going back to the question, I need to identify the causes of frustrations not the frustrations itself. Similar to my experience, IS professionals fail to have a good plan. It might be because they are only focusing on one factor and others are taken for granted. Since we are dealing with information systems, that is why IS planning requires profound analysis and should consider all factors and all the necessary things that would contribute to the improvement. IS professionals may get tired of the unending revisions of IS plan, they should never ignore themselves be dominated by the feeling instead they should keep on working and let the perseverance power over.

My second idea on frequently experienced causes of frustration in IS professionals and users while working on an IS plan is the lack of support from the management or from the personnel. Without the support, the IS professionals efforts would end up in frustration.

New technologies are emerging and old ones are outdated. Many major technologies can have a life expectancy of less than five years. These pressures have resulted in a drive for new approaches to planning and managing information technology (IT) services. That is why many of the organizations right now are having a greater investment in IT and information systems (IS). This is now the moment that organizations would try to hire IS professionals to have analysis and improvement on their information systems to help them compete in the market.

Design systems by IS professionals could also frustrate users in the workplace. Users find it hard to understand and use the implemented system. This frustration can affect workplace productivity, user mood, and users’ interactions with other co-workers. It also can affect their emotional state. These frustrating experiences also harm organizations by undermining productivity, lowering quality, and raising stress levels. Improving user interface design is one clear opportunity and it would benefit many users. To build better interfaces, more user involvement is needed in the interface design process. Designers should follow the interface guidelines that exist. User training will also help, especially if it addresses problem solving strategies that will help build self-efficacy. Even small changes in the interface can make a big impact on user satisfaction. IS professionals should also be better situated as the intermediary and be able to get better information between users and vendors when understanding frustration in the workplace.

Frustration is a natural feeling after all. Even none IS professionals experience being frustrated. It happens all the time when we fail to take the action and/or fail to attain our goals. Our response to it should be adaptive. Adaptive responses are constructive and are implemented to solve the problem that is blocking goal attainment. They may include preemptive efforts to avoid the problem, or once the problem is encountered, problem solving strategies to overcome or circumvent the problem.

And also strategic planning must be inclined with the business plan. Strategic planning is an organization's process of defining its strategy, or direction, and making decisions on allocating its resources to pursue this strategy, including its capital and people. Various business analysis techniques can be used in strategic planning, including SWOT analysis (Strengths, Weaknesses, Opportunities, and Threats) and PEST analysis (Political, Economic, Social, and Technological analysis) or STEER analysis involving Socio-cultural, Technological, Economic, Ecological, and Regulatory factors. According to other source, strategic plan is a document used by an organization to align its organization and budget structure with organizational priorities, missions, and objectives. It is also a process of comprehensive, integrative program planning that considers, at a minimum, the future of current decisions, overall policy, organizational development, and links to operational plans. And according to the project management club, strategic planning is a basic document for planning of different projects and their sub-projects. It is based on the content of the Financing Memorandum (FM) and the Monitoring and Evaluation Matrix attached to the Financing Proposal and translates the two documents into detailed operational terms. A satisfactory strategic plan must be realistic and attainable so as to allow managers and entrepreneurs to think strategically and act operationally. In align with that, strategic plan must be reliable and suitable for the need of the company.

In doing a strategic plan, it is not really known to everyone that there are frustrations that may trigger. Frustrations in a way that it may cause depression and stress to the professionals and users that are doing it. In doing an Information Strategic plan, it is really a must that the user and the professionals doing it must first determine the company’s background and other facts and information that can help and then again be a useful tool for the planning.

Computing systems this era raises high in a short period of time. Though our country is a 5 year behind than those countries abroad, still using internet is a common tool for someone like in communications. And more likely in a business, it is also a trend of using internet and intranet in their operations since it can help progress their company. Now a day, an even small scale business also acquires using internet and computers for their daily routine. That is because it can help them improve their skills and at the same time it can lessen the work load since using computers doesn’t requires much time. Relatively, why I’m discussing those computer trend marketing in such a way, since that industry now a days is a computer based industry, lot of professionals and users must be aware of using computer in such a way that it is one of the basic tools for doing the planning.

As what I have stated in the first question of this slide, during our Management Information Systems 1, we did a strategic planning in one of the pronounce company in the city today. Not only here in Davao this company well known, also to the other sites of the city. During our discussions with the group, we have decided to have each an individual task. From that then, we can focus on our topic. But that was one of the problems we have encountered.

Misunderstanding between tow parties is also one of the frustrations that IS professionals encounter. That is one of the frustrations we have. We didn’t know what to do and on the other side we don’t know the topics of our other group. At the end of the compilation, the report of one is not related to the report of the other one, and in vice versa. We then realize our mistake after we have compiled the technical paper. So how can we let ourselves give the technical paper to the company we have if there and else we don’t understand what we did, how much more to them. If such case, we are then called to be the professionals who done lousy approach to the planning for the company we are required to have the plan. Then the user also, such a way that there were the people involved in that strategic plan, are then also approach us lousy for the mistake of some persons. Like what I said above, strategic plan must be reliable so that the company must excel in accordance to era.

Another frustration that may trigger in the planning of this IS plan is the time. Time problem is not only for this kind of situation. Even in our other subjects, we do have difficulty in time management. Stress may occur if we hear the word “deadline”. That can cause cramming that can cause also mistakes. Time management may not be a frustration if and when it was been managed accordingly. But also time management requires more budget than of any other. Since this planning is suitable and a provider for the company, there is also a satisfaction that it can really cost big. Like our technical paper before. By committing mistakes, another big cost is at stake.

That frustrations I have stated is only my point of view. Since I have encountered strategic planning before, I have then encountered such frustration things like that. And that frustration I have encountered might then encountered by those professionals.

These are all my opinion about the question so let’s discuss about what I have interviewed which is the Davao Light and Power Company, as what we have interviewed he told us that frustrations based on his experience is that communication, if there is no proper communication its hard to make an IS plan. If no good communication between the management and the IS professional its hard to make a good IS plan. He also told that budget is also a factor if no budget allocation it’s hard to make an IS plan. Time is also a frustration as what he told us that time is gold indeed. So basically, those were the frustrations that he identified and discussed.


References:
Wikipedia.org
http://en.wikipedia.org/wiki/Frustration

Business Plan and IS Plan

The question was what should be the nature of the relationship between the business plan and the IS plan? To answer the question I will need information that would answer the question and thus ill be able to decide in my own understanding what should be the relationship between the business plan and the information systems plan. So first we should gather enough information in relation to the said topic so that we could answer it correctly. To start, I will define what a business plan and what is information systems plan or also called strategic planning.

According to wikipedia.org a business plan is a formal statement of a set of business goals, the reasons why they are believed attainable, and the plan for reaching those goals. It may also contain background information about the organization or team attempting to reach those goals.

The business goals may be defined for for-profit or for non-profit organizations. For-profit business plans typically focus on financial goals, such as profit or creation of wealth. Non-profit and government agency business plans tend to focus on organizational mission which is the basis for their governmental status or their non-profit, tax-exempt status, respectively—although non-profits may also focus on optimizing revenue. In non-profit organizations, creative tensions may develop in the effort to balance mission with "margin" (or revenue). Business plans may also target changes in perception and branding by the customer, client, tax-payer, or larger community. A business plan having changes in perception and branding as its primary goals is called a marketing plan.

While strategic planning is an organization's process of defining its strategy, or direction, and making decisions on allocating its resources to pursue this strategy, including its capital and people. Various business analysis techniques can be used in strategic planning, including SWOT analysis (Strengths, Weaknesses, Opportunities, and Threats ), PEST analysis (Political, Economic, Social, and Technological), STEER analysis (Socio-cultural, Technological, Economic, Ecological, and Regulatory factors), and EPISTEL (Environment, Political, Informatic, Social, Technological, Economic and Legal).

Strategic planning is the formal consideration of an organization's future course. All strategic planning deals with at least one of three key questions:

1. "What do we do?"
2. "For whom do we do it?"
3. "How do we excel?"

In business strategic planning, the third question is better phrased "How can we beat or avoid competition?". (Bradford and Duncan, page 1).

In many organizations, this is viewed as a process for determining where an organization is going over the next year or more typically 3 to 5 years, although some extend their vision to 20 years.

In order to determine where it is going, the organization needs to know exactly where it stands, then determine where it wants to go and how it will get there. The resulting document is called the "strategic plan."

It is also true that strategic planning may be a tool for effectively plotting the direction of a company; however, strategic planning itself cannot foretell exactly how the market will evolve and what issues will surface in the coming days in order to plan your organizational strategy. Therefore, strategic innovation and tinkering with the 'strategic plan' have to be a cornerstone strategy for an organization to survive the turbulent business climate.
So for me the relationship between business plan and strategic plan is this:

• Why plan?
– To obtain resources
• Financial
• Facilities – “Capacity planning”
• Staff
– To align IS with the business
– To identify needed applications
– To establish goals, schedules, and milestones in order to track progress
– To provide an opportunity for communication with top management and user management
• Outcomes vs. process?
• Reactive vs. proactive?
• Planning vs. forecasting?
– Forecasting is predicting the future
– Planning is being prepared for that future

Information Systems Strategic Planning
• Establish a mission statement
• Assess the environment
• Set goals and objectives
• Derive strategies and policies
• Develop long-, medium-, and short-range plans
• Implement plans and monitor results

Establish a mission statement
• These are the services that you are responsible for; it is your place in the organization
• It is not what you are supposed to achieve, it is who you are and what you do in the company

Assess the environment(s) . . .
1. The capabilities of the IT department
2. The readiness of the company to use IT
3. The status of our customers, our industry
4. The status of the economy, government regulations, environment, society, etc.
5. Technology

This is similar to a SWOT analysis – Strengths and Weakness – items no. 1 & 2; and Opportunities and Threats – items no. 3, 4, & 5

Goals and Objectives
• Set goals – what do you want to achieve?
• Set objectives – what are your specific, measurable targets?

Derive strategies and policies
• Strategies for
– Technology focus
– Personnel and career development
– Aligning with the company
– Others . . .
• Policies for
– Funding criteria; how much to spend on IT?
– Allocation criteria; priority setting
– Organizational arrangements
– Use of outside IT services, outsourcing
– Selling IT services to outside organizations
– Others . . .

Short-, medium-, and long-range plans
• Short-range – the next year, the next budget period; developing and operating current systems
• Medium-range – committing to development efforts for applications that will take more than one year to complete; meeting management’s current information needs, projected into the future for as many years as needed to complete them. This is what most organizations call “Long-Range Planning.”
• Long-range planning – preparing for management’s future information needs. These are not application specific; they are investments in infrastructure; it is creating an information architecture.

And finally, implement plans and monitor results.

Business planning and strategic planning are very closely interrelated. Business planning can be seen as an aspect of the overall strategic planning of a company, minutely following in written form all the sides of the business. Also, the strategic planning can be seen from the perspective of the business plan of a company as a delineator of main rough, undetailed aspects.

Strategic planning implies general directions of a business, main strategies, a long-term perspective, for about 2-4 years.

Business plans, on the other hand, state in detail the data of the business from the marketing point of view, from the management and personnel point of view and from the financial point of view. They also contain stipulations for contingencies. They offer a shorter term perspective, for about 1 year.

In a world of an ever increasing competition, less stable and predictable, planning has become more important for managers, conditioning business existence. Times are for thorough analysis of a business from all its perspectives, the difference between an evolving business and a failure depends on this.

Even if inclined to base their actions on immediate-gain grounds, successful business managers have learned to take their time for a prospective analysis. Even if initially starting off their business on a gut feeling, successful talented managers have learned that they have to go beyond the gut feeling, putting together a concrete plan of action, meant to enhance more stability and reduce the tendency of working at random.

Although there are voices saying that most successful businesses did not need a plan to begin with, I would not minimize the importance of a business plan, integrated within the strategic business planning, as every business, be it small or "oversized" will need a plan in a certain stage of its growing. The reason might be not necessarily its founding, but the need to communicate in the business environment — be it raising some money or hiring quality personnel.

Basically we can refer to the strategic business planning through the SWOT analysis used for marketing: analysis and identification of strengths, weaknesses, opportunities and threats. Strengths and weaknesses are internal factors of the business, while opportunities and threats are external factors.

The strength analysis requires a look at the advantages of a business, its strong points and all its resources and capabilities that can be used as a basis for developing a competitive advantage.
Weakness may be absence of certain strengths. Weaknesses' analysis must reveal where there is room for improvement, what is there to avoid.

Opportunities and threats are triggered by environmental occurrences such as unexplored marketing niche, new technologies, new loosened regulations, identifiable as opportunities or, on the contrary, threats such as consumers' change in tastes away from the firm's products, new regulations, debt or cash-flow problems, etc.

The business plan treats in detail the main directions that the strategic planning settles. If strategic planning provides general directions for the next 2 years, the business plan analysis what the business' characteristics are, how to implement the directions, what will the impact on the market and the potential customers be, the financial side of the action etc., generally all the ins and outs of the matter.
When starting a business online there are some things you certainly want to know and be able to put in place to offer yourself a much higher chance at success.

The first draft of a business plan for an online venture must include the means and targets you are going to use to drive customers to your business that are more inclined to buy.
It makes sense that just being able to send random people to your business is not going to lead to a high percentage of buyers. This is why we target and the internet gives us the easiest way to find our potential customers and put our products or services in front of them without spending a dime.

Advertising online has much more to do with knowing than it does with spending. There are certainly ways you can spend money online advertising and make a very good return. When starting a business and putting together that first draft of a business plan you want to consider these as well if you can afford them.

You key is going to be spending time looking at the searches people are making every day online as they relate to whatever it is your are trying to use as your online business.

If you are selling bird cages you would want to know what searches people are making and in what frequency in order to craft your website and content to attract those people. This is the key to making money online regardless of what type of product or services your new online business is offering.

So basically, the relationship between the business plan and IS plan is that the IS plan is inclined to what the organization or business is aiming at. They should be related to each other to meet a common goal. So basically that’s it.

References:
Wikipedia.org
http://www.businessplanning.ws/learn/business-strategic-planning.html
http://ezinearticles.com/?Starting-a-Business---First-Draft-of-a-Business-Plan&id=3868596

Playlist