0% found this document useful (0 votes)
80 views7 pages

SOC-Based Solution for SPC Assessment

The document outlines the assessment brief for the module CSE5013, focusing on developing a Service-Oriented Computing (SOC) solution for the State Pharmaceutical Cooperation (SPC). Students are required to compare monolithic and service-oriented architectures, design and develop an application, test it, and explain deployment techniques, with a total word count of 3000. The assessment includes specific criteria for grading and emphasizes the importance of ethical, digital, global, and entrepreneurial skills.

Uploaded by

hqnvpgt26h
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
0% found this document useful (0 votes)
80 views7 pages

SOC-Based Solution for SPC Assessment

The document outlines the assessment brief for the module CSE5013, focusing on developing a Service-Oriented Computing (SOC) solution for the State Pharmaceutical Cooperation (SPC). Students are required to compare monolithic and service-oriented architectures, design and develop an application, test it, and explain deployment techniques, with a total word count of 3000. The assessment includes specific criteria for grading and emphasizes the importance of ethical, digital, global, and entrepreneurial skills.

Uploaded by

hqnvpgt26h
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

School of Technologies

Assessment
Brief
Module Code Module Title
CSE5013 Service Oriented Computing

Academic Year Semester


2024 3

Module Leader email


gihan@[Link]

Content
CONTENT.................................................................1
ASSESSMENT DETAILS.........................................2
SUBMISSION DETAILS...........................................3
ASSESSMENT CRITERIA........................................4
FURTHER INFORMATION.......................................6
Attendance
Who can answer questions about my assessment?...6
Referencing and independent learning........................6
Technical submission problems...................................6
Extensions and mitigating circumstances...................6
Unfair academic practice...............................................6
How is my work graded?...............................................7
Assessment Details
Assessment title Abr. Weighting
SOC based solution for SPC WRIT1 100%

Pass marks are 40% for undergraduate work and 50% for postgraduate work unless stated otherwise.

Task/assessment brief:
State Pharmaceutical Cooperation (SPC) is responsible for pharmaceutical drug manufacturing and
importing to meet national requirements. When SPC wants to buy some kind of a drug it will advertise for
a supplier and the suppliers should submit a tender proposal. Before applying for the tender supplier
must be registered with SPC. Also, SPC has few drug manufacturing plants and planning to increase the
facilities further in the [Link] distributes its drugs via SPC's own pharmacies and also links dealer
pharmacies. SPC is focused on improving its services and operation with the aid of Information
technology and below are some functionalities that are identified by the SPC.

 Supplier registration can be done in any of the main branches and this feature should be added to
the existing website as well.
 Manufacturing plants should be able to update stock details of the warehouse. Also, the
warehouse staff can update stock details based on the externally purchased quantities.
Manufacturing plants are looking to add this feature to their current system. Some plants are
running on web-based systems and others on Windows-based systems.
 SPC and registered pharmacies should be able to search for any drug and also place an order
from the main warehouse. The linked pharmacy network is using some kind of software system to
manage its sales and inventory currently. This new feature should be linked with their systems

Based on the above mention requirement you need to develop a SOC-based solution. Need to
implement needed requirements as services and also need to build client applications and consume via
API. (API project must be developed using .NET technologies and the client application can be built using
.Net or any other platform)

Tasks:

1. Explain how Monolithic architecture and Service-oriented architecture models can be used for this
case study. Compare and contrast both architectures and justify the best architecture based on
maintainability and scalability. (20 marks) (LO1)
2. Design and develop a suitable application based on SOC. Need to implement the services and also
must create a client application to consume the services. Should be able to demonstrate and
provide all source codes with suitable design diagrams. Need to use proper coding standards and
must focus on the reusability and maintainability of the application (60 marks) (LO2,LO3)
3. Properly test the developed application and should be able to demonstrate the debugging process

2
and demonstrate testing results. (10 marks) (LO3)
4. Explain deployment techniques that are suitable for the developed application (Server, Docker,
Kubernetes, etc....). (10 marks) (LO4)

Word count (or equivalent): 3000

This a reflection of the effort required for the assessment. Word counts will normally include source code,
any text, tables, calculations, figures, subtitles and citations. Reference lists and contents of appendices
are excluded from the word count. Contents of appendices are not usually considered when determining
your final assessment grade.

Academic or technical terms explained:


SOC – Service-oriented computing
SOA – Service-oriented application
API - Application Programming Interface. It acts as a messenger between different software applications,
allowing them to communicate and exchange data.

Understand -
Involves grasping the meaning of information, ideas, or concepts. It goes beyond simply memorizing
facts and requires interpreting, explaining, and summarizing the information in your own words.
Design –
Creating something new, whether it's a plan, a process, a product, or a solution to a problem. It requires
using your understanding to generate something original and functional.
Develop –
Creating: This refers to taking an existing design and building upon it, refining it, or bringing it to life. This
involves a high degree of originality and innovation.
Applying: This signifies using existing knowledge or skills to create something new, but not necessarily
something completely original. It involves adapting and implementing existing concepts in a new context.
Evaluate –
This involves making judgments about the value, worth, or effectiveness of something. It requires
analyzing information, identifying strengths and weaknesses, and comparing it to established criteria or
standards.

Submission Details
Submission This will be provided This will normally be 20
Estimated Feedback
Deadline: on the Moodle working days after initial
submission point. Return Date submission.

Submission By 2.00pm on the


Time: deadline day.

Moodle/Turnitin: Any assessments submitted after the deadline will not be marked and will be
recorded as a non-attempt unless you have had an extension request agreed
or have approved mitigating circumstances. See the School Moodle pages for
more information on extensions and mitigating circumstances.

File Format: The assessment must be submitted as a pdf document (save the document as
a pdf in your software) and submit through the Turnitin submission point in
Moodle.

Your assessment should be titled with your:

3
student ID number, module code and assessment ID,
e.g. st12345678 CSE5013 WRIT1

Feedback Feedback for the assessment will be provided electronically via Moodle. Feedback will
be provided with comments on your strengths and the areas which you can improve.
View the guidance on how to access your feedback.

All marks are provisional and are subject to quality assurance processes and
confirmation at the programme Examination Board.

Assessment Criteria
Learning outcomes assessed
 Understand Service oriented architecture and patterns.
 Design service application solution by applying SO concepts
 Develop service service-oriented application
 Critically evaluate the suitable delivery environment and deploy service application.

Other skills/attributes developed


This includes elements of the Cardiff Met EDGE (Ethical, Digital, Global and Entrepreneurial skills) and
other attributes developed in students through the completion of the module and assessment. These will
also be highlighted in the module guidance, which should be read by all students completing the module.
Assessments are not just a way of auditing student knowledge. They are a process which provides
additional learning and development through the preparation for and completion of the assessment.

ETHICAL Understanding the importance of protecting user data within service


interactions. This includes adhering to data privacy regulations and
implementing secure coding practices.
DIGITAL Deconstructing complex problems into smaller, manageable service
components and designing solutions with clear interfaces. Understanding
how cloud platforms can host and manage services, ensuring scalability
and reliability.
GLOBAL Being aware of international regulations and standards that might impact
service development and data handling. Embracing diverse perspectives
and being flexible in adapting service design to meet the needs of global
contexts.
ENTREPRENEURIAL Identifying opportunities to create new businesses or to enhance the
existing process using services oriented application development.

Marking/Assessment Criteria

4
Task Poor Satisfactory Good Excellent
< 40 40 - 54 55 -69 70 -100
Understanding Demonstrates Provides a basic Clearly explains the key Provides a comprehensive
of Architecture, minimal overview of both characteristics and comparison with detailed
Comparison, understanding of architectures, but functionalities of both explanations of how each
and Contrast both monolithic and explanations lack monolithic and SOA architecture addresses the
SOA architectures, clarity and depth. architectures, including challenges of the case study.
confusing key Provides a advantages and Justifies the choice of SOA based
concepts. Fails to superficial disadvantages. Identifies on specific criteria like
compare and comparison, key differences between maintainability (modular design,
contrast the two focusing on generic the two architectures, independent deployments) and
architectures in a differences without highlighting how they scalability (horizontal scaling of
meaningful way. addressing the impact maintainability individual services). Provides a
specific context of and scalability. Explains comprehensive and insightful
the case study. how SOA's modularity comparison, analyzing the trade-
and loose coupling offs between the two architectures
enable easier in the context of the case study.
maintenance and scaling Demonstrates a clear
compared to the understanding of how SOA's
monolithic approach. characteristics directly address the
challenges of maintainability and
scalability for the manufacturer-
supplier communication system.
SOC Application No design diagrams Design diagrams Design diagrams are Design diagrams are detailed and
Design and or documentation are present but clear and accurate, professional-looking, showcasing
Development are provided, lack clarity or representing the the application's structure and flow.
making detail. application architecture Documentation is thorough,
understanding the Documentation is and service interactions. informative, and easy to follow,
application difficult. incomplete or The documentation is including code comments and API.
The code is poorly inaccurate. Code comprehensive and Code is highly modular and
written, lacks demonstrates provides clear reusable, with a clear separation of
modularity, and some modularity instructions for usage concerns and well-documented
makes future but lacks a clear and future. The code is interfaces. Design choices prioritize
modifications separation of modular and well- maintainability and future
difficult. The concerns, making organized, with a clear enhancements. The application is
application lacks maintenance separation of concerns. well-designed and implemented,
core functionalities challenging. The Services are designed with all required functionalities
or is incomplete, application for reusability in potential working seamlessly. The user
failing to implements basic future. The application interface is intuitive and user-
demonstrate the functionalities but implements core friendly. Code is well-structured,
key services lacks key features functionalities with a documented, and adheres to
required for the or suffers from user-friendly interface coding standards.
case study. significant bugs. and demonstrates the
required services.
Testing Scope No testing is Basic testing is Core functionalities are Comprehensive testing strategies
and Coverage conducted, or only performed, but tested with some level of are implemented, including unit,
limited testing is coverage is limited, automation. Debugging integration, and functional testing.
performed on basic and critical skills are demonstrated Testing results are analyzed and
functionalities. functionalities for identified issues. documented. Effective debugging
might not be skills are demonstrated, resolving
tested. issues efficiently.
Understanding Demonstrates Provides a basic Explains suitable Provides a comprehensive analysis
of Deployment limited understanding of deployment techniques of deployment options, considering
Options understanding of deployment options for the developed factors like scalability,
different but fails to explain application (e.g., Server, maintainability, and cost-
deployment their suitability for Docker, Kubernetes) and effectiveness. Justifies the chosen
techniques or the specific their advantages and approach based on the specific
provides inaccurate application. disadvantages. needs of the application
explanations.

5
Further Information Unless stated otherwise you must use the
HARVARD referencing system. Further
Attendence
guidance on referencing can be found in the
Regular attendance is highly encouraged and
directly impacts your learning success in this
Study Smart area on Moodle and at
module. A minimum of 80% attendance is [Link] (use your
expected. university login details to access the site).
Students with attendance below 80% will be Correct referencing is an easy way to
required to showcase their knowelegde as
requested by the module lecturer. Fail to do so improve your marks and essential in
may result of retaking the entire module. achieving higher grades on most
In exceptional cases (e.g., documented medical assessments.
emergencies), alternative arrangements may be
considered. Please discuss these with the module
lecturer as soon as possible. Technical submission problems

Who can answer questions about my It is strongly advised that you submit your
assessment? work at least 24 hours before the deadline to
allow time to resolve any last minute
Questions about the assessment should be problems you might have. If you are having
directed to the staff member who has set the issues with IT or Turnitin you should contact
task/assessment brief. This will usually be the the IT Helpdesk on (+44) 2920 417000. You
Module Leader. They will be happy to answer may require evidence of the Helpdesk call if
any queries you have. you are trying to demonstrate that a fault with
Moodle or Turnitin was the cause of a late
Staff members can often provide feedback on submission.
an assignment plan but cannot review any
drafts of your work prior to submission. The Extensions and mitigating circumstances
only exception to this rule is for Dissertation
Supervisors to provide feedback on a draft of Short extensions on assessment deadlines
your dissertation. can be requested in specific circumstances. If
you are encountering particular hardship
Referencing and independent learning which has been affecting your studies, then
you may be able to apply for mitigating
Please ensure you reference a range of circumstances. This can give the teachers on
credible sources, with due attention to the your programme more scope to adapt the
academic literature in the area. The time assessment requirements to support your
spent on research and reading from good needs. Extensions and mitigating
quality sources will be reflected in the quality circumstances policies and procedures are
of your submitted work. regularly updated. You should refer to your
degree programme or school Moodle pages
Remember that what you get out of university for information on extensions and mitigating
depends on what you put in. Your teaching circumstances.
sessions typically represent between 10%
and 30% of the time you are expected to Unfair academic practice
study for your degree. A 20-credit module
represents 200 hours of study time. The rest Cardiff Met takes issues of unfair practice
of your time should be taken up by self- extremely seriously. The University has
directed study. procedures and penalties for dealing with
unfair academic practice. These are  Use of unacknowledged material
explained in full in the University's Unfair downloaded from the Internet.
Practice regulations and procedures under  Re-use of one’s own material except as
Volume 1, Section 8 of the Academic authorised by your degree programme.
Handbook. The Module Leader reserves the
Collusion, which can be defined as when
right to interview students regarding any
work that that has been undertaken with
aspect of their work submitted for
others is submitted and passed off as solely
assessment.
the work of one person. Modules will clearly
identify where joint preparation and joint
Types of Unfair Practice, include:
submission are permitted, in all other cases
they are not.
Plagiarism, which can be defined as using
Fabrication of data, making false claims to
without acknowledgement another person’s
have carried out experiments, observations,
words or ideas and submitting them for
interviews or other forms of data collection
assessment as though it were one’s own
and analysis, or acting dishonestly in any
work, for instance by copying, translating
other way.
from one language to another or
unacknowledged paraphrasing. Further
How is my work graded?
examples include:
 Use of any quotation(s) from the Assessment grading is subject to thorough
published or unpublished work of other quality control processes. You can view a
persons, whether published in textbooks, summary of these processes on the
articles, the Web, or in any other format, Assessment Explained Infographic.
where quotations have not been clearly
identified as such by being placed in Grading of work at each level of Cardiff Met
quotation marks and acknowledged. degree courses is benchmarked against a set
 Use of another person’s words or ideas of general requirements set out in Volume 1,
that have been slightly changed or Section 4.3 of our Academic Handbook. A
paraphrased to make it look different from simplified version of these Grade Band
the original. Descriptors (GBDs) with short videos
 Summarising another person’s ideas, explaining some of the academic terminology
judgments, diagrams, figures, or used can be accessed via the Facilitation of
computer programmes without reference Learning resource page.
to that person in the text and the source
in a bibliography/reference list. We would strongly recommend looking at the
 Use of assessment writing services, Study Smart area of Moodle to find out more
essay banks and/or any other similar about assessments and key academic skills
agencies (NB. Students are commonly which can have a significant impact on your
being blackmailed after using essay grades. Always check your work thoroughly
mills). before submission.

Common questions

Powered by AI

For a SOC-based application at SPC, suitable deployment techniques include using Docker and Kubernetes. Docker allows encapsulating services in containers, facilitating consistent deployments across environments, thus aiding in manageability and portability . Kubernetes can further manage these containers, providing robust orchestration with features like automated scaling and self-healing, thereby supporting the high availability and scalability required for SPC's operations . These techniques are advantageous as they support the dynamic nature of service updates and scaling, essential for SPC's diverse system requirements .

Implementing API-based communication in SPC's service-oriented application is crucial for ensuring seamless integration and interaction between different systems and services across the organization and its partners . APIs enable standardized, secure data exchange and interaction, which facilitates real-time inventory updates and order processing between SPC’s manufacturing plants and linked pharmacies . The flexibility of APIs also supports scalability, allowing SPC to integrate additional features or third-party services efficiently . These benefits enhance data consistency, operational efficiency, and extend SPC's service capabilities .

SPC can leverage global perspectives by integrating international compliance and user experience standards into their service-oriented technology designs . By adopting globally recognized data privacy and healthcare regulations, SPC ensures their operations remain compliant and competitive in international markets . Incorporating diverse cultural perspectives and user interfaces can enhance usability for a global audience, potentially increasing the reach of their services . Collaborating with international experts can also introduce innovative practices and technologies, promoting advanced service design solutions tailored to broad market demands . These strategies help SPC develop technologies that are globally applicable and future-proof.

Service-Oriented Architecture (SOA) enhances maintainability by providing modularity and loose coupling, allowing independent development and deployment of services which ensures that changes can be isolated, reducing the risk of impacting the overall system . This modular nature also supports horizontal scalability by enabling additional instances of specific services to be deployed based on demand, unlike Monolithic architecture where scaling requires the entire application to be duplicated . These characteristics of SOA directly address the challenges of maintaining and scaling a pharmaceutical supplier registration system by allowing efficient updates and scaling of specific functionalities as needed .

Ethical considerations in developing a service-oriented application for SPC include ensuring the protection of user data and compliance with data privacy laws . Implementing secure coding practices and data encryption protocols is crucial to safeguard sensitive information related to pharmaceutical supplies and suppliers . Additionally, considerations such as transparency in data handling and ethical sourcing of third-party services must be prioritized to align with both legal standards and moral obligations . These measures help maintain public trust and protect against legal repercussions, providing a foundation for ethical IT practices .

Service-oriented computing (SOC) facilitates technological enhancements in pharmaceutical service operations at SPC by providing modular, interoperable services that streamline processes like supplier registration, stock management, and drug distribution . SOC's flexibility allows the integration of new functionalities and systems, such as updating stock details and searching for drugs, without disrupting existing operations . By handling transactions and interactions through APIs, SOC ensures data consistency and accessibility across SPC's manufacturing plants and linked pharmacies, thereby improving operational efficiency and service delivery . These capabilities enable SPC to enhance customer service and optimize supply chain processes .

Key challenges in applying SOC to SPC's drug supply chain include handling the integration of heterogeneous systems across web-based and Windows-based platforms and ensuring real-time data synchronization between various branches and systems . Addressing these issues requires adopting robust API management practices for communication between disparate systems and employing data integration techniques such as middleware to facilitate seamless data exchange . Furthermore, implementing reliable service choreography patterns can orchestrate complex interactions amongst multiple services, addressing synchronization and data consistency challenges . These approaches help minimize integration difficulties and maintain operational efficiency across different systems within the supply chain .

International regulations and standards can significantly influence service development and deployment by necessitating compliance with data protection laws, such as GDPR for data privacy and security . They also demand adherence to international health and safety standards for pharmaceutical data management, influencing the design of services to ensure secure data handling protocols and interfaces . Furthermore, global interoperability standards might require SPC systems to be flexible in integrating with international suppliers and regulatory bodies, thus impacting service modularity and API design . These considerations are crucial for ensuring the developed services can operate effectively across different legal and technical landscapes.

SPC should implement comprehensive testing strategies including unit testing, integration testing, and functional testing to ensure the functionality and robustness of their SOA-based application . Automated testing can improve efficiency and coverage, ensuring that core functionalities and service interactions are consistently validated . Additionally, conducting regression testing during updates and changes in the application helps maintain system integrity . Employing effective debugging processes can quickly identify and resolve issues, further enhancing the robustness of the application . These strategies ensure that the application performs reliably across different usage scenarios .

The separation of concerns in a SOC application benefits SPC's pharmaceutical operations by isolating various functionalities into distinct services, facilitating easier maintenance, updates, and debugging . It allows developers to focus on specific modules without affecting others, improving the system's reliability and scalability . This modularity ensures that new features can be integrated seamlessly and individual components can be scaled independently, which is essential for managing sales and inventory across SPC's pharmacies . Overall, it increases the operational efficiency and adaptability of SPC's IT infrastructure .

You might also like