Sunday, January 29, 2012

Software project: JS feed for joomla - Software Architecture Document

1. Introduction

This document provides a high-level overview of the evolving technical architecture for the “JS Feeds for Joomla” project. The document provides a high-level description of the goals of the architecture, the use cases support by the system and architectural styles and components that have been selected to, best achieve the use cases.

1.1 Purpose

This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions, which have been made on the system.
In order to depict the software as accurately as possible, the structure of this document is based on the “4+1” model view of architecture.


1.2 Scope

This document explains and discusses the architecture of the “JS Feed for Joomla” module.

1.3 Definitions, Acronyms, and Abbreviations

· GUI - Graphical User Interface
· UML - Unified Modeling Language
· Joomla - Joomla is a free and open source CMS or content management system for publishing content on the World Wide Web and intranets. It comprises a model–view–controller (MVC) Web application framework that can be used independently also.
· API - An application-programming interface (API) is an interface implemented by a software program that enables it to interact with other software. It facilitates interaction between different software programs similar to the way the user interface facilitates interaction between humans and computers.
· RSS Feeds - a simple XML-based system that allows users to subscribe to their favourite websites. Using RSS, webmasters can put their content into a standardized format.
· CSM – Content management system.

1.4 References

  • SRS - Software Requirement and Specification
  • Joomla feed Extensions -
  • Working with Google Feed API -
  • Google Feed API -

1.5 Overview

The Software Architecture Document contains the following subsections.
  • Section 2: describes the use of each view
  • Section 3: describes the architectural constraints of the system
  • Section 4: describes the functional requirements with a significant impact on the architecture
  • Section 5: describes the most important use-case realization. Will contain the Analysis Model and the Design Model
  • Section 6: describes design’s concurrency aspects
  • Section 7: describes how the system will be deployed. Will contain the Deployment Model
  • Section 9: describes any significant persistent element. Will contain the Data Model
  • Section 10: describes any performance issues and constraints
  • Section 11: describes any aspects related to the quality of service (QoS) attributes
Full Article(pdf) : PDF DOWNLOAD 

No comments:

Post a Comment