Association of Information Technology Professionals  

AITP 9th Annual National Collegiate Conference
April 1-3, 2004  Omaha, Nebraska

"AITP Programming Contest Rules & Guidelines"

==>Updated March 18, 2004<==

The following rules and guidelines apply to the Cobol, C++, VB, Webpage Design, Java, Database, Systems Analysis & Design, Network Design programming contest events.  For an explanation of the BYOC (Bring Your Own Computer) option fort the contest events - scroll down.

1. Students competing on a team must be AITP members currently enrolled in courses at a two- or four-year college/university. Students who already have graduated from college with a related Bachelor's or Masters degree (CIS, MIS, IS, CS) may not compete. Additionally, we request that IS professionals (excluding internships and co-ops beyond one year) not compete as well. We are also also counting on the AITP student chapter faculty advisors to assist in this area.  However, a new Graduate student paper contest was approved and started with the 2003 conference.  The same rules will apply but scoring will be done for undergraduate .vs. graduate divisions.

                          2. Team Size:  1-2 individuals for  Cobol, C++, Visual Basic, FrontPage2004, Java, Database, Systems A&D, Network Design

3. Teams registering on or before April 3, 2004 pay a $35.00 registration fee per team. Teams registering after that date or onsite pay a $55.00 registration fee per team. Substitutions for members of registered teams is allowed but at the time of team registration, ALL team members must register or already be registered for the conference. Contest team registrations "only" will be "held" until the individual student attendee registrations are received.

4. Teams will have approximately 4 hours to complete their assigned problem or problems. This amount of times INCLUDES registration, briefing, problem statement review, Q&A, the actual contest itself and any contest de-briefing.

5. A team may not consult with nor communicate with anyone outside the team during the contest. Only teams and authorized room proctors will be allowed in the contest labs during the competition and the team's sponsor/advisor may not communicate with the team during the competition.

6. Team members may use printed reference materials of all types which they have brought to the contest. You may not bring any disks, CD’s or any computer media including any electronic devices to the competition area.

7.   A team may only use their assigned workstation unless directed otherwise by the contest proctor/official.

8. Teams must use the software provided by the host site during the contest. Teams may not bring nor request that their own text editors, etc., be installed for use during the contest. The software, editors, etc., will be announced as soon as they are confirmed (subject to change) and all teams will use that common software as provided by the host site.

9. Legitimate special physical needs such as special keyboards, chairs, etc., need to be communicated to the host site and their availability and use negotiated by March 25, 2004.

10. Proctors in the contest labs will give a 15-20 minute warning before the ending time for the contest. Any final printing or other work must then be finished by teams before the announced ending time for the contest. When this ending time is reached, all teams must stop and turn in materials to the room proctor promptly.

11. Teams must turn in all materials provided by the contest coordinators as well as all electronic and printed materials produced by the team in working the contest problems. Teams may not have included the team members names nor the name of the college the team represents nor any other identifying information anywhere in the materials turned in to the proctor. The team's solution and other materials may only be identified by the team number assigned to the team at the beginning of the contest.

12. Any violations of the rules and guidelines will result in the offending team being disqualified. Such disqualification may be ruled by the room proctors, contest coordinators or judges.

13.  Although team feedback will vary by contest event and judges, our goal is to provide maximum team feedback beyond recognizing the top three contest winners. We will rank the top ten teams for each contest event with places 4th through tenth receiving an honorable recognition for their achievements. Sample and/or winning solutions will also be posted on the web site www.aitp.org after the conference. In the event of a tie, the time stamp will be used to break the tie.

14.  Additional contest information (and changes/updates) will be published on the web site www.aitp.org. Additionally, links to web sites maintained by our volunteer base will contain tips, solutions, sample problems….

15.  Graduate students will be allowed to compete in the student paper contest as a separate division.  Otherwise, Graduate students may not compete in any other programming contest events associated with this conference.

16. General programming contest solution judging criteria:

      a.   Only Programs/solutions that function will be initially evaluated (unless no one has a functioning solution).

      b.   Internal documentation refers to descriptive data and module names, readability of code and internal comments  

 


AITP National Collegiate Conference

BYOC: Bring Your Own Computer Rules & Guidelines

  1. All computers (both desktop and laptop computers are allowed) must have Windows XP, Windows XP Professional, Windows 2000, or Windows 2003 installed.  Your computer should be fully patched with all current operating system and application software updates.  It should also have current antivirus software installed to help protect against the possibility of infection and/or corruption that could result in a loss of your competition time, results, or both.

  2. All computers must have a USB port (USB 2.0 preferred, but not required).  Each team is responsible for ensuring that their computer's USB port is functioning properly.  As you compete in a particular contest, you will prepare a folder on your computer that contains your team's work.  At the end of a competition event, the Contest Coordinator will use USB hard drives to collect folders submitted for review by the judges.  The folders cannot contain any identifying indications, other than your officially-assigned team number.

  3.  Wireless or wireline networking devices may not be activated during competition.  Any activation will result in immediate disqualification.

  4.  Some contests may allow or require that printed materials be submitted at the end of the contest period.  See the rules on the official AITP National Collegiate Conference website (www.aitp.org) to determine whether or not your contest will require printed output.  If printing is required for a particular contest, the Contest Coordinator may make network-based printers available at the end of the contest period.  In order to be able to use those printers, your computer will need to have a Category 5 Ethernet cable with RJ45 connectors and a 10/100 Ethernet adapter.  You will also need to have Microsoft Windows Networking and TCP/IP both installed.  The TCP/IP connection properties should be set to use DHCP so that the computer can obtain its network address automatically.

  5.  Your computer must contain the approved application development tool(s) in the version(s) specified on the official AITP National Collegiate Conference website (www.aitp.org).

  6. All teams are responsible for ensuring the safety, security, and integrity of their computer equipment.  AITP does not assume responsibility for any loss or damage.

  7. A testing area will be available adjacent to the overall conference registration table to verify USB, network, and printing capabilities. 


AITP National Collegiate Conference

"AITP Programming Contest Rules & Guidelines"

COBOL Programming Competition

  1. Micro Focus for Windows Net Express Version 3.1, running on a Windows XP Pro platform will be utilized with Office XP 2002 & Text Pad
  2. A program shell (from the Identification Division to the Working-Storage Section header) and data files will be  supplied to each team. A sample of correct output will be available to the teams during the contest.
  3. Basis for Evaluation: Correct Output (60%), Structure & Modularity (30%), Internal Documentation (10%)

Visual Basic Programming Competition

  1. Microsoft .Net 2003 wth MSDN Help, running on a Windows XP Pro platform, will be utilized.  Office XP2002 and Text Pad will also be available.
  2. Basis for Evaluation: Correct Output (60%), Structure & Modularity (30%),  Internal Documentation (10%)

C++ Programming Competition

  1. Microsoft Visual Studio 6 SP 5, running on a Windows XP Pro platform, will be utilized.  Office XP 2002 and Text Pad will also be available

  2. All mathematical formulas and data files will be provided, but students will need to be familiar with  binary files & text files (space delimited & columnar).

  3. The problem statement will include a sample of the correct output

  4. Basis for Evaluation: Correct Output (70%), Structure & Modularity (20%), Internal Program Documentation (10%).

Web Design Competition

**Updated/Expanded/Enhanced SIGNIFICANTLY on March 17, 2004**

  1. Contestants will be required to develop a corporate intra/internet system and submit their URL to the competition supervisor at the conclusion of the contest.

  2. As part of the “Bring Your Own Computer” initiative, contestants will be allowed to furnish their own computer (laptop or desktop) running Windows XP, Windows 2000, or Windows 2003 and development and web server software of their choice.  No network connectivity will be provided so web sites MUST NOT depend on remote resources and may ONLY relay on resources local to the machine.  Please remember that your machine will need to be running some type of web server (IIS, Apache, etc…) and since database connectivity may be required in the problem statement, plan accordingly (MS Access, MySql, etc…).  All computers, web services and database services should be patched to the latest level and proper security measures put in place.

  3. If a contestant chooses not to bring their own hardware, a limited number of computers will be provided with Microsoft FrontPage2002, running on Windows XP with Microsoft IIS HTTP server installed.  The default tools, installed automatically when FrontPage installs itself as a "Typical Installation", are the only features that will be available.  You must contact Mark Grimes (contest co-chair) at mgrimes@bus.olemiss.edu  by 3/29/2004 to secure one of these machines. 

  4. Since the web servers will be running on the machines used in the competition, the computers must be left after the competition to be judged.  Machines will be secured overnight and may be picked up the morning after the competition in a location to be named.

  5. Please be prepared to leave a short document outlining technologies used in development and any special considerations for the website (address of page, passwords, etc…).  Please ensure that your computer will automatically “lock” or password protect itself as we will not be able to judge a machine we can not attain access to.

  6. Basis for Evaluation: Functionality (40%), Ease of Use (30%), Overall Appearance (20%), Ease of Maintenance & Documentation (10%).

 

JAVA Programming Competition

  1. Sun Java 2 (1.4.0) runnong in Windows XP Pro will be used.  Office XP 2002 and Text Pad will also be available.

  2. Areas to be proficient include client-server skills (ability to read and write from a database), API skills (develop an application using a published API), Object-Oriented architectural skills (proper use of composition, inheritance, interfaces and defined classes) and foundation Java programming skills.

  3.  Basis for evaluation; Satisfying Specifications (50%), Implementation & Problem Solving (30%), Internal Documentation (10%), Structure & Architecture (10%).

  4. Refer to www.auldenfire.com/aitpncc/rules.shtml for all the detailed rules and examples.

Network Design Competition

  1.  Competing 1 or 2 person teams will create a proposal for a network design given a problem statement scenario.  Elements will include LAN design, network components, protocols used, security issues and network architecture and a budget.

  2. A workstation with Microsoft Office XP and a proposal template in MSWord on a Windows XP platform will be provided to each team along with a hardware/software inventory list which includes make, model, specifications and prices.  The drawing tools within Word can also be used for the proposal.

  3.  Basis for Evaluation: Functionality (35%), Efficiency (30%), Creativity (20%), Organization of the Proposal (15%).

Database Competition

Teams from one to two individuals will be given a problem statement and approximately a three hour time frame to (1) design the database and (2) implement specified components of that database using Microsoft Access 2002.  The database design will consist of an Entity Relationship (ER) diagram and a relational schema, which will be turned in for scoring.  Teams may use software, such as Microsoft Visio or Visible Analyst, to create the ER diagram, or may draw it by hand.  Each team can bring your own laptop/notebook PC with your own ER diagramming software and bring any needed reference material.  Teams may not use their own computer to complete the implementation component. 

 

The implementation component of the competition will be in Microsoft Access 2002.    After a team has completed the design component and turned in that design for scoring, they will begin working on the Access database, which will contain the populated tables of the database.  The Competition Problem Statement:

·        Will require the students to draw the ER diagram (entities, relationships, cardinality, and optionality) and to specify a relational schema normalized to 3NF, with all keys indicated

·        Will require students to perform operations on Access tables, create queries of various types, develop custom forms, reports, and data access pages.

·        Will require students to develop macros, switchboards, and event procedures.

·        Will describe an application that can be designed and developed in approximately 3 hours

 

The judging will use the following for determining each team’s score:  Design Component (25%), Production Component (75%).

 

"Call for Student Papers"

Individual undergraduate and graduate student papers are solicited dealing with contemporary and important issues in business information systems. Topics include, but are not limited to, software engineering issues, the use of CASE tools, user interfaces, client server, database systems, expert systems, decision support systems, applications of object-oriented, graphical, or visual programming languages, data communications and networks, ethical and social issues, security, and multi-media environments.

Papers for review and publication are limited to fifteen (15) typed, double-spaced pages including figures, tables and references. Paper must use 12 point Times font, be right and left justified, and have 1 inch margins all around. Paper must include a separate cover page with title, name, college and/or university, address, and e-mail address for the author. The first page of the paper must have the title and a list of appropriate keywords such as those presented as suggested topics, but NO NAME or EDUCATIONAL AFFILIATION of the author. A 250 word maximum abstract must immediately follow the keyword list. The body of the paper must contain NO NAME or EDUCATIONAL AFFILIATION of the author. References must appear in alphabetical order at the end of the paper as follows:

Adams, D., Wagner, G., and Boyer, T. (1983) Computer Information Systems: An Introduction, Southwestern Publishing: Cincinnati, OH.

Liebowitz, J. (1995) Integrating Expert Systems Throughout the Undergraduate Curriculum. Journal of Information Systems Education, 7 (1) 34-36.

Senhouse, C. (1995) An Entity-Relationship Design for Graphical Software Development. Proceedings of the 33rd Annual ACM Southeast Conference, Clemson University, SC, 37-41.

They are referred to in the body of the paper as (Adams et al., 1983), (Liebowitz, 1995), and (Senhouse, 1995) respectively.

PAPERS NOT CONFORMING TO THESE RULES WILL BE DISQUALIFIED

Referees are instructed that they are reviewing what is essentially a final paper. No manuscripts will be returned to the authors. The referees will assign point values to the papers. On the back of this flyer, you will find both the criteria for initial paper evaluation and the onsite presentation evaluation points. The combination of these two scores will determine the ultimate student paper contest winners.

Authors will receive notification of acceptance or rejection by March 19, 2004. Only the top ten (10) papers in the competition will be accepted for presentation at the conference. All finalists must register for the conference in order to present. Information on presentations will be sent with notification of acceptance. A group of judges, different from the previous referees, will attend each student presentation at the conference and make the final determination as to first, second, and third place winners who will receive at $500, $250, and $100 respectively for Graduate and Undergraduate competitions (separately).

Email a Word or PDF document of your paper to:  AITP 2004 NCC Student Paper Contest
                                                                             Attn: Sean Gallagher 

                                                                             401 North Michigan Avenue, Suite 2400
                                                                             Chicago, IL 60611-4267

Papers must be postmarked/emailed  no later than February 20, 2004. (Electronic Copies WILL be accepted) to Sean_Gallagher@aitp.org and must also indicate which division (Undergraduate or Graduate) you are competing in.  Finalists will be announced on or before March 19, 2004.


AITP National Collegiate Conference

Student Papers Evaluation Criteria

INITIAL STUDENT PAPER EVALUATION

A panel of reviewers will review your "blind" paper (meaning all identification of the author will be removed) and score the papers on the following points and scale:

Undergraduate: Total possible score of 120 (maximum of 20 points for each category):

Graduate: Total possible score of 100:

ACCEPTANCE AS A FINALIST

You will be notified via email/phone/mail if your paper has been accepted as a "finalist" for presentation at the 2004 AITP National Collegiate Conference in Omaha, Nebraska. In order to present your paper, you must register and attend the conference and appear at the scheduled breakout session Saturday, April 3, 2004, to present your paper.

ONSITE STUDENT PAPER PRESENTATION EVALUATION  (Both Undergraduate and Graduate)

A panel of judges will objectively evaluate your live presentation of your paper during the scheduled breakout sessions on Saturday, April 3, 2004.  Separate presentation sessions will be scheduled for graduate and undergraduate paper presentations and a time block of 15 minutes will be provided for each presentation.  There will be timers and setup time will be available. .

Total possible score of 120 (maximum of 20 points for each category):

DETERMINATION OF WINNERS

The combination of the two scores (paper evaluation and presentation evaluation) will ultimately determine the overall student paper contest winners with the top three scores being awarded first, second and third place.


AITP National Collegiate Conference

"AITP Student Chapter Web Site Contest"

 

*Sponsored by the ICCP Education Foundation

BASIC RULES & GUIDELINES

1.               The solution must be the official AITP student chapter web site representing the school of the students competing.

2.        Remember, the target audience for the site are current and prospective members of your local AITP student chapter!

3.        Only one entry will be accepted per school.  All students from the same school wishing to compete must team up with each other.

4.        All competitors should be active members of their  local student chapter's web site committee.

 

FUNCTIONAL REQUIREMENTS

 

1.        Student chapter officers and information for contacting them

2.        AITP Student Membership form (completed online and submits an email to chapter membership chair)

3.        AITP Student Chapter website listing of other AITP student chapters (searchable database by school/state, use info from www.aitp.org)

4.        Announcements of upcoming events

5.        Past chapter activities - including photos

6.        Meeting minutes - a summary of the most recent chapter meeting

7.        A link to www.aitp.org

8.        Remote announcement update capabilities (finalists only)

 

 

TECHNICAL REQUIREMENTS

 

1.        All content MUST run on your web site.  A link to a form on another web site will not count as meeting a requirement.

2.        Must run on IE 6.0

3.        Must NOT include any plug-ins or other add-ins that must be downloaded and installed in order to use the web site.

4.        PDF files are acceptable content on the site.

5.        Design for the minimum screen resolution of 600x800 (no horizontal scroll bar).

6.        Finalists must demonstrate and show announcements can be updated from a web browser form that does not require any programming knowledge.

 

JUDGING GUIDELINES

 

1.           Functionality - everything on the site should work properly

2.      Navigation

3.      Visual Appearance

4.      Documentation (finalists only)

5.      Content - Useful Information

6.      All Functional and Technical requirements have been satisfied

 

PROCESS

 

1.                    The contest judges will select the top 5 entries (URL submission is due 3/1/2004) to Sean_Gallagher@sba.com. 

2.                    The top 5 entries will be declared "finalists" and will be notified by March 19, 2004.

3.          Late submissions "will not be considered".

4.                    Finalists will present their websites on Saturday, April 3, 2004 as a scheduled breakout session.

5.         We would like for one faculty member from each of the finalists schools to help with the judging at the conference as well.

 

 

TIPS ABOUT COMPETING

 

1.        Design your web site for what it represents.  You may use Flash but it must be appropriate for an AITP student chapter web site.  Don't over do it.  Have a mature professional theme..

2.        Web sites are judged by a point system.  No matter how great a certain feature is, it can only earn you the maximum points for a certain aspect of the contest.  It generally isn't going to be enough to make up for a low point total for another area either.  Don't overlook any category the web sites are judged by.

3.        Give yourself every opportunity to win.  The judges will make every effort to give each web site a fair evaluation but realize that it is to your advantage to be certain your work isn't overlooked.  Don't place any barriers, such as a special login, to the features of your web site.  Contestants don't have the opportunity to explain their web sites in the initial phase when the finalists are being selected.  Be aware of the situation and make sure everything is as obvious as possible.

4.        Finalists will be asked to provide written web site project documentation at the finalist presentation for the judges.        

 

 

CONTEST URL SUBMISSION (Must be by 3/1/2004!!!)    Email: Sean_Gallagher@aitp.oprg

 

 

CONTEST QUESTIONS???        Email: mike@burell.com

 

 


AITP National Collegiate Conference

"Systems Analysis & Design Contest"

You can bring your own notebook PC ideally with a NIC card for networking printing capability.  Purdue Universities pc's will have Microsoft Visio already installed for your use and convenience.

Teams of one or two individuals will be given a business problem statement and approximately a three hour time frame to analyze and design. Any widely used methodology may be used such as Object Oriented Analysis, Structured Analysis, Information Engineering, Prototyping, etc. The business model does not have to be fully implemented; however, a system design that allows user prototyping with screen/window/web page interaction will be considered in the over-all grading.

This contest is software and methodology independent. Each team can:

C   Bring your own laptop/notebook PC

C   Bring your own business modeling software.  This could include any CASE, I-CASE or other model-based

   development product.  Example tools may include: Oracle Designer/Developer, Unified Modeling Language,

   Visible Analyst, CA Cool Gen, Cool Jex, etc.

C   Bring any needed reference material.

 

 

The Contest Problem Statement:

C    Will allow multiple analysis and design methodologies, which may include structured analysis,

   object-oriented analysis, information engineering, rapid application design and prototyping and

   any other widely accepted methodology

C     Will describe a corporate problem that can be solved in approximately 3 hours

 

Each team will provide a set of analysis and design diagrams for the problem statement depending on the methodology selected and/or followed.  Total points will be used to determine the overall contest winners.

 

The judges will use the following criteria in evaluating team your solution depending on which methodology was selected:

                                                  -----------METHODOLOGY 1-----------                                          -----------METHODOLOGY 2------------

Overall

%

Structured/Info. Engineering

%

Object-Oriented Approach

%

Unique Approach

10

Correct Entity Relationship Diagrams (ERD's)

35

Class Diagrams, State Charts, Sequence & Activity Diagrams

70

Correctness of Overall Solution

30

Process Models (Decomposition, DFD's, Dependency, Process Action Diagrams..)

35

Design Model (Windows, Screens and/or Web Pages)

20

Completeness

30

Interface Design Models

20

Prototyping Capability

10

Acceptability

30

Prototyping Capability

10

 

 

 

100

 

100

 

100

 For additional information, contact Dr. Bill Tastle, contest coordinator, at tastle@Ithaca.edu.