In our latest blog we spoke to Andreas Symeonidis and Kyriakos Chatzidimitriou Project Coordinator and Technical Coordinator, respectively, as they discuss the real-world benefits of S-CASE at the recent NetFutures event in Brussels.
We started by asking them what the biggest user need, or pain point, that S-CASE addresses?
Kyriakos: Imagine you and your friend are, for example, co-founders in a small mobile development shop. Your real technical expertise is in the development of mobile apps, but for almost all of your projects you need some back-end services running on the cloud in order to upload or download user data and contact 3rd party web services.
Andreas: It could be some weather services needed for your latest app, say.
Kyriakos: Not being web service tech-savvy, you’ll either have to outsource the back-end development, which will cost you more money, or you’ll have to do it yourselves which slows down time-to-market.
Is this where S-CASE comes in?
Andreas: Practically, there is the potential risk of under performing, especially in terms of reliability and security. And you know how competitive and unforgivable the mobile market can be! You would almost certainly adopt an open source solution that would help you alleviate this pain, wouldn’t you? Especially one with an active community, some successful case studies and a well documented website with lots of tutorials and examples. In a nutshell, this is exactly what S-CASE is all about!
How will the S-CASE solution really benefit the end-user?
Kyriakos: S-CASE would help you build robust and scalable back-end web services for your mobile apps. We’ve been users of S-CASE for almost a year now and we’ve started to see several benefits in action.
Andreas: We can avoid writing boilerplate code for our RESTful web services, which reduces lead times. Also, S-CASE incorporates good design practices and patterns in our codebase. Through S-CASE, we keep requirements and the respective source code always aligned, which has been really great to see happening in actuality.
Kyriakos: External web services were never easier to use, really. We can now add to our codebase, almost automatically, the web service we want by just describing the functional and non-functional requirements it must satisfy.
How does S-CASE achieve this?
Andreas: S-CASE is able to recommend a list of services to select from. So that even though your apps may be customized per client, the back-end services are quite similar in terms of functionality. Through S-CASE you are able to identify similar functionality and re-use requirements, code and web services for every new app you build.
Kyriakos: Building back-end services has never been easier. In fact, seeing how S-CASE has facilitated our workflow, we also pitched it to our friends working on pure Web API development.
Thanks very much.
Both: You’re welcome.
To find out about S-CASE involvement at other developer-focused events, or to find out more about the project in general be sure to take a look at the project blog. Andreas and Kyriakos work at the Aristotle University of Thessaloniki who are coordinating the S-CASE project. NetFutures engaged several project and for more information look here.