Transcript Course Outline

Business Information Systems
Research Project in Information Systems
(IS4401)
2008 / 2009
This week
• Have draft proposal ready
• Allocation of supervisors to students
• Establish schedule for weekly project group
meetings
• Initial feedback from supervisors
What are we aiming at?
“Underlying the expectation of performance
increases is the belief that information can
be captured and disseminated throughout
the organisation more quickly to help
individuals do their jobs better by making
better decisions”
Arnold, V. (2006), Behavioural research opportunities: Understanding the impact of
enterprise systems, International Journal of Accounting Information Systems, draft
accepted Feb 2006
FYP 2007 segmentation
2007 FYP Projects
Project category
Total
Marketing & Sales
34
Business process
30
Customer data Mgt
21
Performance reporting 12
Supply Chain mgt
6
Grand Total
103
FYP 2008 segmentation
2008 FYP projects
Sector
Services
Hospitality
Club / Association
Education
Retail
Public sector
Financial services
Manufacturing
Professional services
Technology
Media
Travel
Grand Total
Total
22
19
17
15
12
7
4
4
4
4
2
1
111
Coaching sessions
• Thursday 2nd Ocotober (Don O’Leary, Google)
– Importance of customer requirements
– System specification
– Innovation
• Thursday 9th October
– Picking a database
– Development environments
• Thursday 16th October
– Web-site hosting and implementation
– Other technologies
Proposal guideline
•
Objective : aim of the project
•
Project client, name of company if relevant
•
Requirements : describe problem domain / business need
•
Scope of project proposed : what it does / doesn’t cover
•
Benefits for users : speed, efficiency, control, quality, ...
•
Technical specification:
–
–
–
•
Data requirements (eg. Customers, products, ...)
Interface requirements (does system need to talk to other systems)
Technologies used (hardware, software)
Proposed timeframe
FYP proposal guideline
•
Scope of project proposed : eg. inventory control for car repairs business
•
Objective : eg. automate sales order processing and purchase orders so that
spare parts inventory is always up to date
•
Project client or sponsor (eg. Dunmanway Motors Ltd.)
•
Requirements : eg. ability to record and transmit sales and purchase orders
accurately and with minimal errors, real-time view of inventory levels
•
Benefits for users : eg. single source of data entry, better control of spare parts in
stock, reports (for sales, purchasing and inventory)
•
Technical specification:
–
–
–
•
Data requirements (eg. customers, products, ...)
Interface requirements (does system need to talk to other systems)
Technologies used (eg. ASP.net for development, MySQL for database)
Proposed timeframe (Analysis & Design, Development, Test, Implementation)
Frequently asked questions
•
•
•
•
•
•
Are there more marks for an innovative project?
How do I get the best marks?
Can the project be for a placement company?
Does project have to be for a real-life company?
Can I use non-standard technologies?
Can the project be done as part of a larger system?
When doing a project for a company
•
•
•
•
•
Make sure the requirements are clear
Set-up a reliable communication channel
Client feedback on system is vital
Ensure that the final handover is clean
You must be able to demo the system here!
Software Available 2007/2008
Development tools
Front-end Tools
Productivity Tools
Applications
Java Control Plug-in 1.4.2
FrontPage 2002
MS Project 2003
MS Dynamics GP 9.0
Java Developers Kit 1.5.0
MS Image Composer 1.5
Minitab 14 (statistics)
Microsoft SQL 2000 client
Dreamweaver 3.0
NetMeeting 3.01
Oracle 10g client
Paint Shop Pro 6
Visio 2003
Telnet QVT 4.0 (Unix emulator)
Internet Explorer 7.0
Windows XP SP2
ConTEXT Java editor
MS Web Publishing
Acrobat Reader 7.0.7
jGrasp 1.8.3 Java editor
Mozilla Firefox 1.7
Microsoft Office 2003
Java Developers Kit 1.4.2
Winzip 8.1
Sun Java Wireless Toolkit 2.2
MiKTex (desktop publishing)
J2 SE 1.5.0
Knoppix (Linux environment)
J2 EE SDK 1.4
DataStream 4.0
Net Beans IDE 5.0
MS Visio 2003
Visual Developer Suite 6.0
LaTEX
Visual Studio .NET 2005
TestOut client
Technologies : non-standard s/w
• Requirement should first be cleared with
supervisor (use standard s/w or laptop)
• Software must be licensed: written approval from
technical staff first!
• Any machine “compromise” is resolved by
cloning!
• Machines in Lab 1.12 are shared, therefore
installing specific software doesn’t make it your
machine