REFLECTIONS
Week One to Week Two Reflections
Week
One
Actual
Results
Lecture: Week one comprised of
basically going through outline, what was expected of us with this unit,
the how marks are allocated. Project evaluation was also defined and basic
introduction into what the unit is about.
Reflection
In reflection the first week like all units was pretty
introductory going through the do's and don'ts of the unit and what we expected
as well as what was expected of us. The tut was basically a mad rush to enter
into the lab but that was quite similar to most other units. However most of the
units with labs seem to be like that. So basically the lecture interested me in
the sense that we are going to compare operating systems and packages in this
unit.
Week
Two
Actual
Results
Lecture: Week two basically introduced us to Business Analysis
which also happens to be our assignment topic.
Tutorial: Consisted of grouping and confirming members
of the group picking the topic in which we are doing Business Analysis basically
finding websites relevant to this topic and posting them on the bulletin board.
Reflection
I felt this lecture went a bit quick there seems to be
a lot to be covered though however I have read through the lecture notes again
to enforce the main points given. As we have picked the topic on the subject of
Business Analysis this section should be more familiar to us.
As we are finding more relevant web sites on this topic
this is also helping our understanding on this topic. It is I have also found it
quiet interesting how this unit and Systems Analysis and Design have similarities
such as this area analysing business and the means of analysing a business.
Week Three to Week Four Reflections
Week Three
Actual Results
Lecture: Week Three the topic focused on hardware and selecting software. Firstly we went through the means of the methods of selecting hardware, such as using benchmarks such as those on the manufactures sites (www.Intel.com) or Tomshardware.com which supposedly gives a less bias benchmark of certain hardware such as processes for example (Pentium VS Athalon). Benchmarks also helps consumer or business, know what their getting from the product and also allows them to have a good idea that they are getting the right product for the purposes they need it for. Software is also next taken into consideration such as the type of operating system platform for the server (OS2, UNIX. Windows Based), and client (Windows based Win98, Win95, Win2000, WinNT, Unix based Solaris, Redhat, OS2 based OS2 warp). Also the type of accounting software that would be best suited to the business such as MYOB, Quicken, Microsoft Money, etc. Although we are concentrating on MYOB in this unit. So we went through the minimum hardware requirements needed to run MYOB and the recommended requirements and which is the latest version of MYOB. Also what type of addition hardware would be suited or useful such as Zip drives (or any other portable storage media), and printer, network card (network system). Lecture then went into a more in-depth evaluation of processors, from the Pentium series analysing different voltages each have the bus speed they are in MHZ cache size, and processor speed. Ram was also briefly explained evaluated noting there are many different types of ram Simms, Dimms, Edo, SD, etc. Hard drives were also main points were also pointed out from the seek time to the spindly speed which has helped us understand the difference between hard drives, apart from the obvious fact that there are difference with size of hard drives. Lastly the lecture explained monitors and input devices, input devices being (mice, keyboards, modems) monitor sizes and they where also compared from the Super VGA which most of us use to XGA, and LCD.
Tutorial: Consisted mainly of presentations in which I learnt a lot about the topic each topic people had presented, from the topics of SWOT analysis which refers to a method of analysis of comparing the strengths weaknesses, opportunities and threats, and the advantage of this method Vs the Pest method. Also the presentation on Information technology strategy was very helpful going and looking into some of the business websites that were listed gave a really good explanation of what types of different strategies were available and what strategies are most suited for which situation. Application portfolio was also presented which gave a pretty thought explanation of the old dos platform based applications that are still available and those that are more predominate today such as MYOB. Basically the rest of tutorial was spent doing our case studies in which I have to admit we were behind, though we have now caught up.
Reflections
I thought that this weeks lecture was very interesting as I have just recently registered a computer business, dealing with repairs and piecing together new computers. So this lecture on hardware I found was interesting because it backs up the experience and knowledge I had while working in a computer shop and being a technician as well having my own experience with my own computer. I also found the section on computer operating system platform quiet interesting as I have probably installed all Microsoft operating systems and have been curious for a while but lazy to take up Linux. However overall I always find lectures about hardware and software very interesting and I felt this lecture I understood more and was becoming more interested in this unit. I also found that the presentations are good because it reinforces what has been done in the lecture in a way that is probably easier to follow for the student.
Week Four
Actual Results
Lecture: Lecture four, converted the main topic of Evaluation of Networks. This firstly this converted comparing products which the involved the three factor cost, performance and feasibility for the firm. What was also interesting was the components of a simple network in which hardware side (hub and wiring and different types of wiring) of a the desktop was explained computer with a network card running a windows based Os or Unix or Os 2 based operating system. Specifications for the server were also described as well as wot applications were going to either run on the server or what files were going to be stored on the server. Basically a good server system was described from file access, to Internet to applications that may be run on the server with the Internet such as Lotus Notes. Server operating system platforms where also identified and compared such as Windows NT, to Novell to Unix and Linux from the cost to the difference for the number of users licensed to the reliability. Network protocol such as TCP/IP - OS) and IPX where explained in some detail the layers that comprised of them and which was most popularly used today. Land area networks such as less than 30 computers and how to install a LAN and wot sort of software would be used across one.
Tutorial: again the presentations continued, with good presentations both on evaluation of hard drives and ram in which Tom's hardware was quoted as a good benchmark to use. And Seagate website gave a good explanation of hard drive specifications and speed. Ram was also evaluated from the type or Rams such as SD, EDO, DIMMS, SIMMs, etc and what they are used for their speed and what are the most popular type of rams at the moment.
Mick then gave us personal help on our websites if we needed it due to the complexity of WebCT, so we could get our websites up and edit them easily in a way.
Reflections
I felt this lecture like the last one was one a topic I'm quite interested in it seems to have a lot of the same content as our Ec203, with the section on wiring, layers, protocols, which I found good because it reinforces what I had learnt that the week before in Ec203. Again operating systems and platforms interest me so this lecture was a more an insight. I also plan to do something in network in the future hopefully a network consultant so the areas on how to set up a small network and what applications would be run across this small network were really informative. As well as the protocols being used, TCP is probably the most widely used protocol basically for the use of Internet, my experience with IPX is I have only ever used it to play LAN games as it seems to be the protocol for games to run on a LAN. I think basically this week has been really useful because it goes though the background or more detail of what I'm doing in my other units such as EC202 which we are using Lotus Notes environment, and Ec203 in which we are dealing with networks.
Week Five to Week Six
Week Five
Actual Results
Lecture: Our lecture this week concentrated on the topic of security and evaluation of softwares. Basically the important points about security was how it was broken down into Operating systems, and Application. And what means and methods we could use to protect the operating system such as encryption, error diagnostics. And for applications this would include, recovery or backup, access control, backup facilities for example.
Basically the one that stood out most in my mind was virus scanners and firewalls. This is because most of us are connected to the internet now and it seems we are more susceptible to viruses and denial of service or hackers.
The next part of the topic was about software categories, it is basically broken down into applications packages to tailer made specialised software.
And basically the costs of both of these, such as weighing up whether it is cheaper to have a designed program for the whole firm or purchasing a software package such as Microsoft Office which would have to licensed on each individual computer. Or approaching a consulting service to design the program.
Basically being able to measure the two up using a selection criteria. And what would be included in this selection criteria such as is there good software quality?, how much resources was using in developing the software, was it easily obtainable, is it portable ?, etc. This would be given a rating such as good, bad, excellent, poor, or minimal. Questions need to be answered such as whether the criteria meets users requirements and security questions such as for example does the software help block outside threats or does it allow for access control.
Tutorial: Was basically we did software categories, which was quite interested going to some websites that gave examples of software categories such as design and gave example of software such as Microsoft Paint or Adobe Photo shop and it gave usually gave a brief explanation of which version they had used and what it was capable of doing. The means of exampling software categories using these examples makes it a lot easier to explain and understand, as well as the fact we had another web site which had shareware software available for us to download to rest and try out any category of software.
The tutorial was then moved to time allocated for our websites in which we worked on or updated.
Reflection
I thought this topic was very interested I have always been interested especially in software security in protection and sometimes a bit into the amateur hacking using the Trojan virus. So software such as conseal firewall or other firewall programs were quite interesting to download later after this tutorial this gave a really good idea or indication what packets were entering and exiting your computer as well and thus trying to block these areas. I also found that categorising software can be quiet interesting and involving, I didn't really think that so much needed to be questioned or asked to really evaluate a software and I didn't know it had to fall under certain criteria. So this is another topic I felt wasn't too out of my range, it was interesting because I again had a bit of prior knowledge so this just built on that knowledge.
Week 6
Actual Results
Lecture: The topic was about Functional Evaluation of software and basically learning how to use the software score sheet. This basically expands on the knowledge of software criteria learnt from last lecture. It started with giving a brief explanation of how a software can be examined by looking at a few quick points such as. Whether the supplier is credible or the product itself is credible for example is alot of other firms using it or has it been rated well by software magazines.
Also it can be evaluated by looking at or drawing a product map where operating system would communicate with the product and the data storage and how this would be either effective or not effective. Basically there were three types of different diagrams didnt really understand them though or how they were drawn. NExt a list of supplier strengths and weaknesses such as relying on your experience and judgement on software.
Next we go on about the scoresheet, in which has the purpose of evaluation, rating, and objectively determining the package being evaluated. There should also be a proposed checklist made up and this is used to give a rating or a final score. We next went though how the scoresheet works to tell u the truth it still baffles me.
Tutorial: Our group presented on ISO 9126 and other groups presented ISO 9000 and other stuff to me I really didnt get a gist of much of it however I understood that its basically created to enforce a conformity in global standard that has good regular standard of quality. However I find this to be some what hypocritical and sometimes an image thing more than a means of keeping a good high standard. Because its quiet expensive to go though with ISO 9000 it seems to discrimate with firms who can afford to bare those costs. However Iam really baffled by all the standards and I think it just makes it more confusing having so many long draw standards which seem to cover so many areas that its sometimes quite riduculous.
Reflection
Reflecting on this topc isnt not one of my favourites thats for sure. I found that it was really hard to understand the whole method of evaluating software the concept is quite tedous though it makes sense. I think the score sheet is really far too complicated I felt for what it was trying to achieve and what questions it was aiming to answer. The tutorial I felt again was also quit tedious because the standard especially the ISO standard was really quiet boring even though the knowldege of it was really quite essential going though in too much detail really left me boggled and bored. Anyhow I guess it is important lecture because it thought us how to do the software sheet for our assignment.
Week
7 to 8
Week
7
Lecture: Was basically about the topic of
Feasibility and Risk Assessment. This outlined the types of things that came
with doing a feasibility such as tasks, tests, reports, and why a project may
happen to fail. Risk is also outlined showing the types of risks such as risk
concept risk perception, and the types of risk involve in processes, etc.
Each topic outline was then gone though such as the
system option which I perceived as the options available to firm such as a overall
or a slight upgrade etc. Plus the fact of how change would be expected, and if
the option was scaleable.
An introduction of feasibility was then put forward as
it being the first stage of the project evaluation process. The questions that
should be posed when doing a feasibility which I thought was important for
example "Will it work satisfactorily ?", or "Is it a good
investment". Simple but important questions that need to be posed for ever
type of feasibility to begin and proceed forward. Feasibility Tasks were then
listed from having appointment to producing a functional and operational
requirement to producing a project charter which is the final stage this would
include project scope.
Next we went though what was involved in feasibility
testing and the several important aspects of feasibility that needed to be taken
into account. These are Organisational feasibility, Economic Feasibility, Technical
Feasibility, Social Feasibility, Schedule Feasibility, Legal, Ethical
Feasibility.
The lecture then continued on to talk about feasibility
reports and basically how to structure one the norms in writing one of these
reports and what should be contained in them.
Next also the situations that could arise from a failed
contingency plan if the feasibility happens to fail and also identifying the
possible causes of unsuccessful projects, as well as the Risk involved and how
it is important to consider the possibilities of danger or threats to the
project.
Risk was then expanded by going though the concept of
risk, then the subjectivity of them and how to do a risk analysis chart or
checklist, or the risk assessment or quantifying risk, the response to risk such
as the inherent size or plan.
Tutorial: The tutorial contained the our
interesting presentation on Feasibility report it, and the others presenting on
risk and Feasibility study. Our presentation contained we gave examples on a
bridge and the feasibility of it in San Francisco and this was the basis for the
other web site which was showed how to do the outline of a proper feasibility
report and what needed to be included in one. Plus the importance of what a
feasibility report achieves.
Reflection: This topic is quite important for
our assignment because it is a field that is needs to be address when one a firm
is thinking about upgrading or spending on an area of the firm.
It was also quite interesting because it again overlaps
with my other unit Systems Analyse and Design in which we have to put a minimum
and recommend computer technical requirements down.
Week
8
Lecture
The lecture was on Request for Proposal, this had and
involved Procurement Strategies which included the Request for Quotation,
Request for Information, and Request for Proposal.
Procurement strategies where expanded on this included
questions such as know what your buying and
know exactly what you want (RFP), Don't know what your buying know the
requirement (RFI), Know what your buying (RFQ).
RFQ is basically known "say what you want tell you
how much". First is general information, timelines and deadlines,
Instructions to respondents, and Proposal contents.
RFI is used for product research, used to verify H/W
and S/W strategies, used to gather information about implementation, used to
gather vendor information, etc.
RFP is legally binding, specifies requirement for the
system, specifies method for purchasing the contract, and how many transactions.
Technical Section - Part 1, Description of current operation,
Provide specific volumes, Provides specific examples.
Technical Section - Part 2, Description of proposed
environment, Make requirements functional in nature, response time must be
within 2 seconds.
Management Section - Project management plan, site
preparation responsibilities, delivery and acceptance, maintenance, Training,
Documentation, Vendor must provide documentation.
Price Section - Application software, System software,
System hardware, and Communication.
Appendices - Volume of transactions, workflow analysis,
current communication infrastructure, and corporate standards.
RFP - How much time available / cost, how much is enough
time for writing proposal?, take time to respond too.
Technical Content - Workflow analysis, Provide current
workflow process, Don't provide the answers. Account system - transaction an
hour and minute.
Proposal Evaluation Strategies, provide evaluation criteria
or not, requirement and evaluation points together.
Subjective Evaluation, follows the letter or the spirit
of RFP, can you work with this group.
Objective Evaluation - meeting mandatory administration
requirements, pricing models.
Tutorial
The tutorial I have to admit I had a systems analysis
test and I couldn't arrange to be at the tutorial even though I had some
information on Invitation to tender that my other group members had done and I
had read up on.
Reflection
Though the lecture I felt was pretty boring it did hold an important impact on our assignment in which we have to do a RFI and we have to know what is included in an RFI and how to structure one. So I felt it was important though boring. However the topic will in future be important when being a systems developer or doing other systems analysis units.