Download as a PDF

administrative and security issues which we were unable to
address due to lack of time and resources. These topics
include (a) planning for periodic backups, (b) creating
profiles for different kinds of users working on the registry
(such as DEVELOPER, AUDITOR, OPERATOR,
MANAGER, etc.), (c) adding security provisions (mirroring
sites, redundant disks in the same location), (d) identifying
threats (disruption, destruction, disaster, unauthorized
access), (e) assessing the risk of each threat and preparing a
response for each case, and (f) creating controls to mitigate
or stop threats (consider redundancy, fault tolerant servers,
disaster recovery plans, anti-virus software, security policy,
passwords and encryption, firewalls, etc).
In addition, the instructor may consider alternative methods
of implementation emphasizing, for instance, public relations
issues behind filing complaints against merchants, and the
processing of those complaints, verification of all data,
deleting records from the system, and attending consumer
requests for information. Other major variations closely
related to this project can include similar registries such as a
National Do-Not-Email, Do-Not-Mail, Do-Not-Fax, and DoNot-SMS/Text-Me.
Even with our failure to cover some activities – normally
included in actual software development projects – we
believe that this experience is not only appropriate and
feasible but fun for the students who enthusiastically
embraced the problem and worked towards interesting
solutions.
6. REFERENCES
Balena, Francesco (2002), Programming Microsoft Visual
Basic.NET (Core Reference). Microsoft Press, ISBN 07356-1375-3.
Chikofsky, Eliot (2005), "Reverse Engineering: A Valuable
Double-Edged Sword." Foreword for Eldad Eilam's
Reversing: Secrets of Reverse Engineering. Wiley.
Hansen, Evan (2004), “US Court: Reverse engineering is
‘presumptively legal’ “.CNET News.com, 11:40 BST,
March 01, 2004.
Herreid, Clyde Freeman (1994), “Case Studies in Science A
Novel Method of Science Education”. Journal of
College Science Teaching (pp. 221-229), February.
Martin, C. Dianne and Elaine Yale Weltz (1998). "From
Awareness to Action: Integrating Ethics and Social
Responsibility across the Computer Science
Curriculum. Third Report from the Project ImpactCS
Steering Committee". Available at
http://www.seas.gwu.edu/~impactcs/paper3/pg1.html.
Accessed August 2005.
Microsoft Corp. Technical Articles 175168 and 316675.
Microsoft Knowledge Database.
“Rules and Regulations Implementing the Telephone
Consumer Protection Act of 1991”. U.S.A. Federal
Communications Commission. CG Docket No. 02-278,
Report and Order, 18 FCC Rcd 14014 (2003).
Rumbaugh, James, Ivar Jacobson, and Grady Booch (2005),
Unified Modeling Language Reference Manual, The,
2nd Edition. Addison Wesley Professional. ISBN:
0321245628.
AUTHOR BIOGRAPHIES
Victor Matos is an Associate Professor of
Computer and Information Science at
Cleveland State University in Cleveland,
Ohio.
Rebecca Grasser is an Associate
Professor of Information Systems at
Lakeland Community
College in
Kirtland, Ohio.
Appendix A: Changing a Directory to Allow WebRequested Read/Write Operations
The Internet GUEST account (IUSR_MACHINE), which is
by default part of the "Everyone" group, does not initially
have write permissions on remote database files (.mdb). This
is the most common reason for the exception “Operation
must use an updatable query”. To fix this problem, use the
Security tab in Explorer to adjust the properties for this file
so that the Internet Guest account has the correct permissions
(Microsoft Knowledge Database)
1. Global Change from Basic to Advanced Sharing
Properties
1. Execute the Windows-Explorer.
2. Select Tools | Folder Options | View
3. Uncheck the entry “Use simple file sharing
(recommended)”.
4. Apply | OK.
2. Select Directory and Allow user
1. Select directory that contains the shared file.
2. Right-Click on the folder.
3. Choose Properties | Security
4. Click on Add… to enter anonymous web user.
5. Enter the line <MachineName>\aspnet. Where
MachineName is the machine on which ASP.NET is
installed on.
6. Click Check Names … to verify the validity of the
(anonymous) user name.
7. Select the aspnet user you just created and give him/her
Modify and Write access to the directory.