Scribd
Upload
126 views4 pages

Ictweb518 A1

The document outlines requirements for creating XML documents for product uploads, including: - Creating two XML files, one each for weather and news widgets - Including widget name, description, dates, license, support for multiple images, and Exentu author for each product - Images are optional for some widgets that have self-explanatory descriptions - Support for adding multiple images to widgets that demonstrate with images - Including a category for each widget product - Allowing easy changes to the author name using a code

Uploaded by

Ardra Asok
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
126 views4 pages

Ictweb518 A1

The document outlines requirements for creating XML documents for product uploads, including: - Creating two XML files, one each for weather and news widgets - Including widget name, description, dates, license, support for multiple images, and Exentu author for each product - Images are optional for some widgets that have self-explanatory descriptions - Support for adding multiple images to widgets that demonstrate with images - Including a category for each widget product - Allowing easy changes to the author name using a code

Uploaded by

Ardra Asok
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Task 1 – Specified Requirements for Exentu8:

 Two Well-formed XML documents for product uploads to the website.


 For their main Product Categories – one for weather widgets and one for
international news widgets
 Product should contain widget name, description, date created, date
updated, licence term, support for multiple images and Exentu8 as the
author of the product.
 Not all the widgets have images.
 In some cases, description is self-explanatory, so the document should
have images as an optional requirement per product.
 There should be options for adding more than one image. Widgets that
have demonstration images usually have more than one images.
 There should be category tied to each of the widget products in each
XML file.
 An easy support for changing the author’s name in each widget, use a
shortcut code that can easily be changed and managed by the company.

OFFICIA
L
Task 2 – Project details confirmation email
Client Project Requirements Confirmation Email
Date: 20/02/2022
Subject: Confirming the Project Requirement Specification for the Xml
Document Preparation.
To whom it May Concern,
We have received your email requesting for the Xml document to be
prepared for your Products. I would like to introduce myself Ardra, new
Developer at Leading-Edge working on your project. I would like to confirm
with you about the requirements needed to be covered in the project. According
to the email I have gathered the requirement list as below:
 Two Well-formed XML documents for product uploads to the website.
 For their main Product Categories – one for weather widgets and one for
international news widgets
 Product should contain widget name, description, date created, date updated,
licence term, support for multiple images and Exentu8 as the author of the
product.
 Not all the widgets have images.
 In some cases, description is self-explanatory, so the document should have
images as an optional requirement per product.
 There should be options for adding more than one image. Widgets that have
demonstration images usually have more than one images.
 There should be category tied to each of the widget products in each XML file.
 An easy support for changing the author’s name in each widget, use a shortcut
code that can easily be changed and managed by the company.
I would like you to confirm or if there is anything to add on top of this
above requirements, please send me an email. Once I get a confirmation from
your side, I can start working on the project asap.
Between now and then, if there are any clarifications or additional information
required, we will be in touch with you.
Best regards
Ardra Ashok
Software Developer

OFFICIA
L
LeadingEdge

Task 3 - Establish project timelines in-line with requirements


1. Your selected design methodology and SDLC
Choosing the design Methodology for the project:
I would like to choose “Data Structure-Oriented Design”, utilizes the data
structures of the input data, internal data (for example databases) and output
data to develop software. In the data structure-oriented approach, the emphasis
is on the object, which is the data. In this project, the main goal is to develop the
xml data structure for the project. So, the Data Structure oriented design is the
best for the project. The structure of information, called data structure, has an
important impact on the complexity and efficiency of algorithms designed to
process information.
Data structure-oriented design have a few tasks - evaluate the characteristics of
the data structure, represent the data in its lowest form such as repetition,
sequence, or selection, map the data representation into a control hierarchy for
software, refine the control hierarchy and then develop a procedural description
of the software.  Data structure-oriented design is best utilized in applications
that have a well-defined, hierarchical structure of information. So, data
structure-oriented design is the best for this project.
For SDLC, as the project is simple, short and the objective is very clear and
with stable requirements, I prefer to choose Waterfall development method.
Waterfall being the earliest and the simplest of all the SDLC methodologies.
The whole software development process is separated into phases,
each phase beginning only when the previous one is completed. Every stage has
its own project plan and relies on the information from the previous stage. The
main SDLC stages of this model include gathering and analysing the
requirements, system design, implementation, testing, deployment, and launch.
Such a model is widely used in software development as it is simple to plan and
manage. The process is also strictly documented, and the processes and
outcomes of each stage are clearly predefined.

OFFICIA
L
2. The project timeline
ID Phase Start Date End Date Duration Predecessor
1 Planning 26-02-2022 26-02-2022 2hrs Receiving the Job
2 Analysis 27-02-2022 27-02-2022 2hrs Planning
3 Design 04-03-2022 04-03-2022 4hrs Analysis
4 Implementation 05-03-2022 05-03-2022 2hrs Design
5 Testing and Integration 05-03-2022 05-03-2022 4hrs Implementation
6 Delivery /Deployment 06-03-2022 06-03-2022 1hr Testing and Integration
7 Maintenance Monthly Monthly 1hr Delivery/Deployment

OFFICIA
L

You might also like