Deakin SIT223 - Tech Stack, Ethical Issues, and Project Analysis

This report provides an overview of a group project focusing on asset tracking software development within the context of SIT223 - Professional Practice in Information Technology. The report begins by acknowledging the challenges in finding information for the project and then outlines the chosen technology stacks: Stack A (Java, .NET) and Stack B (PHP, SQL). It details the programming languages, libraries, frameworks, and IDEs used in each stack, along with UI design tools. Security issues, particularly those related to cloud services and web-based software, are discussed, along with the strengths of the chosen technology. The report also addresses the opportunities and risks associated with the project, including data storage and potential system failures or hacking. Furthermore, it analyzes ethical issues, such as data manipulation, favoring vendors, and manipulating stock numbers. The report concludes with a list of references supporting the analysis. The assignment is designed to demonstrate the student's understanding of technology stack design, ethical considerations, and project management within the IT field.

PROFESSIONAL PRACTICE
IN IT
NAME OF THE STUDENNT
NAME OF THE UNIVERSITY

Over view of the activities of the
group:

Issues:
 There are not much information is available
about the asset tracking software
development.
 So it was so much difficult to make plan and
implement that.

Technology stack A:

Technology stack B:

Programming languages for
stack A:
 Programming languages:
 Java,.NET
 Libraries, technologies and
framework:
 Java: JEE/J2EE, Java 2D
 .NET: Visual basic

Programming languages for
stack B:
 Programming languages:
 PHP, SQL
 Libraries, technologies and
framework:
 PHP: CakePHP, Zend
 IDE:
 Komodo, Aptana Studio

UI design tools:
 Graphic and web design:
 InDesign, Corel Draw
 Indesign, Falsh

Security issues:
 The technology stack A and stack B
are having some weaknesses too as
the software will be based on the
internet or web. The software will also
based on the cloud services. The will
be a strong probability to be hacked.

Streangth:
 The technology stack A will be suitable for the
implementation of the project. As it is having
so much advantages. As it will use My SQL as
the data modelling tool but for the stack B
TOAD will be used where My SQL is better
than any other data base modelling tools. And
for the management and planning of the
project MS project will be used where
ScrumDesk is not as good as MS project.

Opportunities:
 The data will be stored into one system. The
authority can access data any time from
there. The data will be stored automatically
to the system and it will send the data
automatically to the storage. There will be no
risk for loosing the data.

Risks:
 The system can have the probability to be
hanged. And the data can be lost then.
And the most dangerous threat for the
software is hacking.