I’ve not done anything at all on Sys. Anal. yet, so I thought I’d do that now.

As always, the first lecture was mostly admin, so I’m actually starting this post from slide 11.

The first thing we’re given is an explanation of what a system is.

An information system is a collection of interrelated components that collect, process, store and provide as output the information needed to complete a business task.

–Satzinger, 2004

Basically, everything you do with your computer is evoking a system. You’re inputting data, the computer processes it, stores and gives confirmation on that. I wouldn’t even say an “information system” had to be a business task.

For every system there needs to be some bare minimal things:

• A goal: something that needs to be achieved
• Elements: Some type of hardware or software that does something
• A way to input data that needs to be processed
• A way to output the results

The flow of data within a typical system. DMU holds copyright, even if it is a feeble image.

Every system has a boundary. In this case it’s a closed boundary, meaning the processes and entities of the system are all internal. That means that all the data is modified using internal systems only. The environment is all the external things that could have an influence on how the system acts, including the inputs from the user.

An input could be the user typing in some data, or automatic data from a … weather beacon. The output would be however the data should be formtated so it’s more helpful information. The process inside is what every manipulation of data there is to be done.

I’ve honestly no idea what control flows and controls are, so if anyone could comment here telling me, I’d be really happy. It doesn’t seem to be a big thing anyway, so I’ll move on.

Inside that boundary there’s only one system going on, but in reality you’d probably have sub-systems too. The more sub-systems, the more complex the operation is. For instance, we imagine the library as one big system. The boundary would probably be the building itself, since all operations here can be done from inside. However, there are many different processes all going on at once within the library; lending books, letting “users” to use a computer, etc.

All systems have the following:

• Hardware
• Software
• Data
• Processes
• People

We know what hardware and software are; the things that the user can manipulate to use the system. Data is the raw material that we feed into the system. The processes are the things that manipulate the data. Users are the end users who will benefit from the system.

That’s pretty much it for that lecture. It was just basically introducing us to what a system is.

The library online catalogue says the course book has eight copies availiable, but I can’t find them anywhere where they’re supposed to be, so I’m using a book on the same topic, but by Thomson Course Technology.